postmortem — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited postmortem (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
After an important bug or failure, capture what happened and why so the same class of problem can't quietly recur. Blameless: the target is the system and the gap, not who typed it. The output is one archivable markdown file.
superpowers:systematic-debugging — don'tdocument the symptom or the first plausible guess. The postmortem is only as good as the cause it names.
commit/PR that fixed it, and the timeline if order mattered.
thing that would have caught or blocked it: a test, a guard/validation, a CI gate, a CLAUDE.md note, or a durable memory.
../<repo>-notes/postmortems/YYYY-MM-DD-<slug>.md.Internal docs are never committed (see standards) — archive it, don't ship it.
# Postmortem: <short title>
- **Date:** YYYY-MM-DD
- **Severity:** low | medium | high
- **Impact:** who/what was affected, for how long
## Incident
<one paragraph: the observable failure>
## Timeline (only if order mattered)
- HH:MM — …
## Root cause
<the underlying cause found via systematic-debugging — the "why", not the symptom>
## Fix
<what changed; commit / PR reference>
## Prevention
<the specific thing that stops this class of bug recurring>~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.