Fedora Linux Triage
Diagnose Fedora server or workstation problems with systemd, dnf, journalctl, SELinux, and firewalld using copy-paste commands and verification steps.
Overview
fedora-linux-triage is an agent skill for the Operate phase that diagnoses and resolves Fedora issues using dnf, systemd, and SELinux-aware guidance.
Install
npx skills add https://github.com/github/awesome-copilot --skill fedora-linux-triageWhat is this skill?
- Step-by-step triage using systemctl, journalctl, and dnf with optional Fedora release input
- Remediation sections with copy-paste-ready command blocks and validation after each change
- Explicit SELinux and firewalld considerations for common Fedora failure modes
- Structured output: Summary, Triage Steps, Remediation, Validation, Rollback/Cleanup
- Accepts optional constraints input to tailor safe remediation under change windows
- Six numbered instruction steps in the core workflow
- Five-section output format: Summary through Rollback/Cleanup
Adoption & trust: 8.5k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Something broke on your Fedora box and you need a disciplined triage path instead of random forum commands that ignore SELinux or firewalld.
Who is it for?
Solo operators debugging a single Fedora host—failed units, package drift, permission denials, or network policy blocks.
Skip if: Non-Fedora distributions, large fleet automation without hands-on shell access, or pure application-level bugs with no OS symptoms.
When should I use this skill?
Triage and resolve Fedora issues with dnf, systemd, and SELinux-aware guidance when the user describes a Linux host problem.
What do I get? / Deliverables
You get a verified remediation plan with journalctl and systemctl checks, applied fixes, validation commands, and rollback steps documented in one pass.
- Numbered triage plan with remediation and validation command blocks
- Rollback or cleanup steps after configuration or package changes
Recommended Skills
Journey fit
Production and local Fedora environments fail in ways that need structured triage—not greenfield feature work—so Operate is the natural home. Errors subphase fits incident-style diagnosis, remediation command blocks, and post-change validation before you iterate on the app.
How it compares
Use for Fedora-specific interactive triage—not as a substitute for observability stacks or Terraform-defined cloud infra.
Common Questions / FAQ
Who is fedora-linux-triage for?
Indie builders and small teams maintaining Fedora workstations or servers who need expert-shaped runbooks without hiring dedicated Linux admins.
When should I use fedora-linux-triage?
In Operate when services fail after deploy, dnf transactions break, SELinux audits spike, or you need validation and rollback commands before closing an incident.
Is fedora-linux-triage safe to install?
Check the Security Audits panel on this page; always review suggested privileged commands and test rollback steps in staging when constraints allow.
SKILL.md
READMESKILL.md - Fedora Linux Triage
# Fedora Linux Triage You are a Fedora Linux expert. Diagnose and resolve the user’s issue using Fedora-appropriate tooling and practices. ## Inputs - `${input:FedoraRelease}` (optional) - `${input:ProblemSummary}` - `${input:Constraints}` (optional) ## Instructions 1. Confirm Fedora release and environment assumptions. 2. Provide a step-by-step triage plan using `systemctl`, `journalctl`, and `dnf`. 3. Offer remediation steps with copy-paste-ready commands. 4. Include verification commands after each major change. 5. Address SELinux and `firewalld` considerations where relevant. 6. Provide rollback or cleanup steps. ## Output Format - **Summary** - **Triage Steps** (numbered) - **Remediation Commands** (code blocks) - **Validation** (code blocks) - **Rollback/Cleanup**