Home › All rules › Community › Arch Linux Copilot Instructions

Arch Linux Copilot Instructions

Guidance for Arch Linux administration, pacman workflows, and rolling-release best practices.

Community rule file, not a RuleStack original. From awesome-copilot (github/awesome-copilot), file instructions/arch-linux.instructions.md. Contributed by awesome-copilot contributors. Copyright GitHub, Inc. Used under the MIT License; the notice is reproduced below and on our licenses page. Shown as written; we filtered it but did not write or test it. Imported 2026-10-17 from commit cb64ad1.

MIT License notice

MIT License

Copyright GitHub, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

How to use

Save this as .github/instructions/arch-linux.instructions.md in your project, commit it, and GitHub Copilot will apply it to matching files. Review it first: community files can be opinionated or out of date.

Note: Review and test before use. Provided as is, without warranty. See Terms.

.github/instructions/arch-linux.instructions.mdDownload

---
description: 'Guidance for Arch Linux administration, pacman workflows, and rolling-release best practices.'
applyTo: '**'
---

# Arch Linux Administration Guidelines

Use these instructions when writing guidance, scripts, or documentation for Arch Linux systems.

## Platform Alignment

- Emphasize the rolling-release model and the need for full upgrades.
- Confirm current kernel and recent package changes when troubleshooting.
- Prefer official repositories and the Arch Wiki for authoritative guidance.

## Package Management

- Use `pacman -Syu` for full system upgrades; avoid partial upgrades.
- Inspect packages with `pacman -Qi`, `pacman -Ql`, and `pacman -Ss`.
- Mention AUR helpers only with explicit cautions and PKGBUILD review reminders.

## Configuration & Services

- Keep configuration under `/etc` and avoid editing files in `/usr`.
- Use systemd drop-ins in `/etc/systemd/system/<unit>.d/`.
- Use `systemctl` and `journalctl` for service control and logs.

## Security

- Note reboot requirements after kernel or core library upgrades.
- Recommend least-privilege `sudo` usage and minimal packages.
- Call out firewall tooling expectations (nftables/ufw) explicitly.

## Deliverables

- Provide commands in copy-paste-ready blocks.
- Include validation steps after changes.
- Offer rollback or cleanup steps for risky operations.

Arch Linux Copilot Instructions

How to use

Related rules

Agent safety guardrails Windsurf rules

Universal vibe-coding guardrails

Prototype-to-production hardening AGENTS.md

Ascii Simulation Game Cursor Rules

Clean Code Cursor Rules

Code Guidelines Cursor Rules

Get new rules weekly