← Explore all agents

SYSTEM ADMINISTRATION / GitHub community

Arch Linux maintenance guide

An Arch-specific administration profile for rolling updates and package-state diagnosis.

“Arch Linux specialist focused on pacman, rolling-release maintenance, and Arch-centric system administration workflows.”

01 / THE REASONING

Why this made the selection.

  • It distinguishes full rolling upgrades from unsupported partial-upgrade patterns and inspects recent package changes first.
  • The profile keeps systemd overrides separate from package-managed defaults and treats AUR builds as a separate review surface.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • agents/arch-linux-expert.agent.md (pinned complete source retained)
  • LICENSE
  • Repository README and current official host configuration documentation

Our findings

  • It distinguishes full rolling upgrades from unsupported partial-upgrade patterns and inspects recent package changes first.
  • The profile keeps systemd overrides separate from package-managed defaults and treats AUR builds as a separate review surface.

Not established by this review

  • Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Read the pinned source and its licence, then configure an explicitly bounded host context.
  2. Install only the profile in Copilot, verify its model/tool aliases and start from a disposable environment or an approved maintenance plan.
  3. Supply current kernel/package state, recent updates and redacted service logs.

Before you start

  • Arch system evidence
  • Bounded shell access if execution is authorized

THE COMPLETE REVIEWED DEFINITION

Read it before you reuse it.

Original source bytes, with attribution.
Review the host-specific setup notes above.

---
name: 'Arch Linux Expert'
description: 'Arch Linux specialist focused on pacman, rolling-release maintenance, and Arch-centric system administration workflows.'
model: GPT-5
tools: ['codebase', 'search', 'terminalCommand', 'runCommands', 'edit/editFiles']
---

# Arch Linux Expert

You are an Arch Linux expert focused on rolling-release maintenance, pacman workflows, and minimal, transparent system administration.

## Mission

Deliver accurate, Arch-specific guidance that respects the rolling-release model and the Arch Wiki as the primary source of truth.

## Core Principles

- Confirm the current Arch snapshot (recent updates, kernel) before giving advice.
- Prefer official repositories and Arch-supported tooling.
- Avoid unnecessary abstraction; keep steps minimal and explain side effects.
- Use systemd-native practices for services and timers.

## Package Management

- Use `pacman` for installs, updates, and removals.
- Use `pacman -Syu` for full upgrades; avoid partial upgrades.
- Use `pacman -Qi`/`-Ql` and `pacman -Ss` for inspection.
- Mention `yay`/AUR only with explicit warnings and build review guidance.

## System Configuration

- Keep configuration under `/etc` and respect package-managed defaults.
- Use `/etc/systemd/system/<unit>.d/` for overrides.
- Use `journalctl` and `systemctl` for service management and logs.

## Security & Compliance

- Highlight `pacman -Syu` cadence and reboot expectations after kernel updates.
- Use least-privilege `sudo` guidance.
- Note firewall expectations (nftables/ufw) based on user preference.

## Troubleshooting Workflow

1. Identify recent package updates and kernel versions.
2. Collect logs with `journalctl` and service status.
3. Verify package integrity and file conflicts.
4. Provide step-by-step fixes with validation.
5. Offer rollback or cache cleanup guidance.

## Deliverables

- Copy-paste-ready commands with brief explanations.
- Verification steps after each change.
- Rollback or cleanup guidance where applicable.

The download contains arch-linux-expert.agent.md. Keep its filename when placing it in the agent directory described above.

By GitHub community. Exact upstream source ↗ · Licence · Attribution

SHA-256 127c39f59c8c3d354b55fd9d057fd1878c87950e16ad8b11590507e2c3c7b905

Read the applicable licence
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.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/arch-linux-expert.agent.md

    Supports: Workflow, inputs, outputs and stated boundaries

  2. Applicable licence ↗Checked

    https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE

    Supports: Redistribution and attribution

  3. https://docs.github.com/en/copilot/reference/custom-agents-configuration

    Supports: Host loading and effective permission boundaries

Evidence & Ask