linux-opslisted
Install: claude install-skill pv-ca/linux-ops
# Linux Ops
Administer this machine so that every change is **recorded**, can be **undone**, and can be **explained later** by a session that has none of this conversation.
Every tool call re-reads this whole conversation, so the number of calls is the cost. Each script below answers in one call what would otherwise take several: use it instead of assembling the answer by hand, and put commands that belong together in one call.
## 1. Tools
Scripts are in `scripts/`, relative to this skill. They need only `python3`, and work on any distribution. Their output is short text meant to be read as is; `--json` exists for when you need every item.
| Situation | Run |
| --- | --- |
| Start of the work, when no `linux-ops host:` line is already in context | `journal.py context` |
| Before the first change of a task | `state.py snapshot` |
| A persistent change | one call: `<apply> && <validate> && journal.py record --what … --undo … [--backup …] [--verify …]` |
| Undo, or "what did you (or an earlier session) change?" | `state.py plan [--since YYYY-MM-DD]`: the active changes newest first with their undo commands, the snapshot from before them, and what still differs from it. One call; do not rebuild it from `list`, `show` and the journal file. |
| After undoing | `journal.py undone <id>` for each, in the same call as a final `state.py plan` |
| "It worked before and now it doesn't", "what changed?" | `state.py list`, then `state.py diff <name>` with the newest snapshot taken **be