reset-triage
Skill0 starsChanged 3 months agoMITView on GitHub
Detects whether the previous boot ended cleanly, and if not, surfaces a standard evidence bundle unprompted. Use on every "I'm back" session start, chained after handover's read-mode — regardless of whether a handover.md was present, since an unclean shutdown can happen outside any planned-reboot flow.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- end-sessionSkill
- etc-driftSkill
- handoverSkill
- host-checkSkill
- incidentSkill
- security-privacy-checkSkill
- update-checkSkill
- vendor-updateSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 51
No output → previous boot ended cleanly.
- Very specific: line 95
Do not attempt a diagnosis or fix here.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Generic, reactive half of this project's crash/hang forensics capability
(thinkpad-fedora-agent decision D33). The permanent baseline sensors that
make this possible — pm_trace, the sysrq bitmask, pm_debug_messages,
and a loosened journald sync interval — live in
hosts/thinkpad-e14-gen5/quirks.sh and are checked separately by
/host-check. This skill's only job is: did the last boot end badly, and
if so, hand over what was already captured. Follow-up on any specific
signature is case-by-case and out of scope here — see the relevant
incidents/ entry or open a new one.
When this runs
Invoked from the handover skill's read-mode, after that skill's own
present/absent branch on .claude/handover.md — both branches, since an
unclean shutdown isn't tied to whether a handover file exists. Not a
standalone entry point; don't invoke this before handover has run.
Detection
last -x | awk '
/^reboot/ { n++; if (n==2) exit }
/crash/ { print; exit }
'last -x reads wtmp and explicitly marks a login session line crash
instead of a clean end-time range when no matching "shutdown system down"
record exists for it — i.e. the machine came back up without ever writing
a clean shutdown record. The reboot lines themselves do not carry this
tag on this system: a reboot entry just perpetually reads still running
once no shutdown record follows it, which is true both for the genuinely
current boot and for a crashed prior boot that never got a matching
shutdown record — so filtering on reboot lines (an earlier version of
this skill did) can never see a crash (see incidents/I018). The actual
signal only ever shows up on the tty/login session line.
The awk scans from the top of last -x (most recent first) and stops at
the second reboot line it sees — i.e. the boundary where the boot-before-
last starts — printing and exiting immediately if it hits a crash line
before that boundary. This bounds the check to the current boot + the one
immediately before it, so older unclean boots already further back in
last -x history (triaged in a prior session, or predating this skill)
don't get re-surfaced.
- No output → previous boot ended cleanly. Say nothing about this — no report, matching this project's no-news-is-no-report norm for routine skills. Move on silently.
- A line printed, ending
- crash (duration)→ unclean. Continue to evidence collection below.
Caveat: this assumes roughly one login session per boot (true here — GNOME autologin into a single Ptyxis/Claude session). A boot with multiple login sessions, or one where the crash happened before any login, can throw off the line-counting; treat this as a good-enough heuristic, not a guarantee.
Evidence collection (only when crash is found)
Gather, in order:
journalctl --list-boots --no-pager | tail -3— confirms the boot IDs and start/end timestamps for the crashed boot and the one before it. Watch for an end timestamp earlier than the start timestamp on the crashed boot — that'spm_trace's bogus-RTC side effect firing, itself a positive signal that the trace actually caught something.journalctl -b -1 -k --no-pager | tail -60— kernel log tail of the crashed boot, the most direct signature of what was happening right before it stopped.journalctl -b -1 -k --no-pager | grep -i "hash matches"— thepm_tracedevice identification line, if armed and it caught a suspend/resume-path hang specifically. Empty output is normal if the hang wasn't in that path, orpm_tracewasn't armed that boot.journalctl -b 0 -k --no-pager | grep -i "hash matches"— same check on the current boot's dmesg, sincepm_trace's identification line is written by the kernel on the boot after the trace fires, not into the crashed boot's own log.
Reporting
Surface this unprompted, in the same register as handover's "Immediately next" — first thing said back to the user, not buried after a recap:
- State plainly that the previous boot ended uncleanly, with its timestamp and duration.
- Give the
pm_tracedevice signature if step 3/4 found one — that's the single strongest lead. - Otherwise give a short characterization of the kernel log tail (last subsystem active, any obvious error/panic line) rather than dumping the full 60 lines into the reply.
- Do not attempt a diagnosis or fix here. If this looks like a recurrence
of a known open investigation (check project memory /
incidents/for a matching signature), say so and point at it. If it looks new, suggest opening one rather than improvising a response — the follow-up is inherently case-by-case per D33 and doesn't belong in this skill.
Why last -x, not a custom heuristic
Considered comparing boot-to-boot timestamp gaps or checking for a
"Reached target Shutdown" journal line directly, but last's crash
marker already does exactly this classification from wtmp, is a single
cheap command, and is what s2idle investigation's own hangs already
showed clearly (confirmed against boot 711aacda from I-series
incidents: last -x marked it crash correctly while the two clean
reboots either side showed normal time ranges).
The first version of this skill filtered on last -x reboot, which
turned out to never carry the crash tag on this system (see the
Detection section above) — it went undetected until a real crash on
2026-08-20 was missed on the first "I'm back" check and only found when
the user reported it manually. Fixed to scan the tty/login session lines
instead. Lesson: a heuristic "confirmed against" one incident still needs
re-verifying against the next one — a single past match isn't proof the
field being filtered on is the right one.
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
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.

