agentleFS
Sign inStart free
jctotsjctots/thinkpad-fedora-agent/.claude/skills/etc-drift/SKILL.md

etc-drift

Skill0 starsChanged 3 months agoMITView on GitHub

Check whether etckeeper actually committed the last change to /etc — an uncommitted /etc change is irreversible in practice per CLAUDE.md, since etckeeper's git history is what makes docs/recovery.md Card 2 possible. Use after any system-touching session, or when the user asks to check /etc drift or etckeeper status.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run scripts/etc-drift.sh from the repo root and show its output as-is.

    line 6
  2. Very specific:

    Run this reflexively after any session that touched /etc, unit files, or polkit rules — CLAUDE.md's own working rules call this out …

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run scripts/etc-drift.sh from the repo root and show its output as-is.

It needs root to read /etc's git state (git -C /etc status / log), via pkexec rather than sudo — this script has no TTY to prompt against when run non-interactively, and pkexec is CLAUDE.md's rule for root commands anyway. Expect the GNOME polkit dialog to appear on screen. It's genuinely read-only but still an ask-tier command per .claude/settings.json — that prompt is expected and correct, not a bug. The default check action never runs etckeeper commit or writes anything; it only reports.

Three possible outcomes:

  • /etc is not a git repository — etckeeper was never initialised. This is the state a fresh install is in until docs/bootstrap.md §3.8 runs; show the printed rpm-ostree install etckeeper + etckeeper init commands and ask before running them (a layered package + reboot, real host mutation).
  • Uncommitted changes found — show the diff-shaped output and offer scripts/etc-drift.sh fix [message], which commits directly via pkexec etckeeper commit (a single reversible commit to an existing repo, same trust level as gpu-toggle.sh) — runnable by the agent or the user standalone; ask before running it, same as any other /etc write.
  • Clean — nothing to do, just report it.

Run this reflexively after any session that touched /etc, unit files, or polkit rules — CLAUDE.md's own working rules call this out explicitly ("after changing anything under /etc, confirm etckeeper committed it").

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free