Arch Linux Triage

Arch Linux triage

Diagnose an Arch Linux problem report, transform update and constraint details into a rolling-release-safe triage plan, and return copy-paste-ready remediation, validation, and rollback commands.

When to invoke

• "Triage this Arch Linux failure."
• "Fix a pacman or broken upgrade problem."
• "Debug an Arch service after a recent update."
• "Why did my Arch kernel update break boot or drivers?"
• "Give me Arch remediation commands with rollback."

Request facts to capture

Preserve these original inputs when they are supplied by the caller: ${input:ArchSnapshot}, ${input:ProblemSummary}, and ${input:Constraints}. If any are absent, collect equivalent evidence with read-only commands.

A step-by-step triage plan should still stay small enough to validate after each major command.

Triage command map

Remediation patterns

Rolling-release safety rules

• Treat partial upgrades as unsupported; prefer a coherent full-system update when package state is involved.
• Read Arch News before major manual interventions when core packages, kernels, Python, OpenSSL, or filesystem layout changed recently.
• Keep rollback grounded in the package cache under /var/cache/pacman/pkg/ or a known snapshot from the user's environment.
• Include reboot guidance whenever kernel, initramfs, graphics driver, systemd, glibc, or low-level libraries changed.

Output template

## Arch Linux triage result

**Status:** diagnosed | remediated | blocked
**Snapshot/update context:** `<ArchSnapshot or collected evidence>`
**Problem:** `<ProblemSummary>`
**Constraints:** `<Constraints or none stated>`

### Summary
<one-paragraph diagnosis and risk statement>

### Triage Steps
1. `<read-only command>` — <evidence expected>
2. `<read-only command>` — <evidence expected>

### Remediation Commands
```bash
# precheck
<command>
# change
<command>
```

### Validation
```bash
<command proving the fix>
```

### Rollback/Cleanup
- **Rollback/Cleanup**
```bash
<command to undo, downgrade, reboot, or clean up>
```

Quality gate

• ${input:ArchSnapshot}, ${input:ProblemSummary}, and ${input:Constraints} were used or marked unknown.
• Recent updates and environment assumptions were checked before remediation.
• Triage used systemctl, journalctl, and pacman where applicable.
• Kernel update, initramfs, module, or reboot considerations were addressed when relevant.
• Every major change includes validation and rollback or cleanup commands.
• No partial-upgrade remediation was recommended without calling out the risk.