post-mortem
100 / 100 · Low risk
Fine to try.
Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Engineer-audience, code identifiers welcome. Use after a debug session lands a fix, before closing the ticket. Trigger on /post-mortem, when the user says "write the post-mortem / postmortem / RCA / root cause analysis", "document this fix", "write up the root cause", "close out this bug with a writeup", or hands you a fixed-and-validated bug and asks for the writeup.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'post-mortem' ] || [ -L ~/.agents/skills/'post-mortem' ]; then echo 'A skill folder named post-mortem already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/danchamorro/pi-agent-toolkit' "$d" && git -C "$d" checkout --quiet 'b762a116c343f012c9b23009a7f2d9af217b8b00' -- 'dotfiles/personal-skills/engineering/post-mortem' && mkdir -p ~/.agents/skills && cp -R "$d"/'dotfiles/personal-skills/engineering/post-mortem' ~/.agents/skills/'post-mortem' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'post-mortem' ~/.claude/skills/'post-mortem' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/danchamorro/pi-agent-toolkit/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-10 | b762a11 | 100 |