post-mortem SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
post-mortem from pitimon/8-habit-ai-dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pitimon/8-habit-ai-dev/post-mortem@git:20260914.5d5e0e3Pins git:20260914.5d5e0e3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pitimon/8-habit-ai-dev
- Path
plugin/skills/post-mortem/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260914.5d5e0e3, committed Sep 14, 2026
- First version recorded
- Jun 8, 2026
- Size
- 13,405 bytes
- Repository stars
- 3
- License
- MIT
Canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Use AFTER a debug session lands a validated fix, BEFORE closing the ticket — produces an engineer-audience artifact. Refuses to draft without a reliable repro, known root cause, identified fix, and validated outcome. Maps to H4 (Win-Win — engineer-to-engineer deposit) + H7 (Sharpen the Saw — capture learning for future-you).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Post-mortem (ชันสูตรบั๊กหลังแก้) **Habit**: H4 — Think Win-Win + H7 — Sharpen the Saw | **Anti-pattern**: Closing a fix with "Fixed in PR #N" and walking away Canonical engineering record of a bug fix. Written **after** debugging lands a validated fix, **for** other engineers (and future-you, who forgets everything in 6 months). Code identifiers are first-class here — this lets the next person grep back to the cause in seconds, not hours. ## When to Use - After a debug session has clearly landed a fix and the fix is validated. - `/post-mortem` invoked explicitly. - User says "write the post-mortem / postmortem / RCA / root-cause analysis", "document this fix", "close out this bug with a writeup". - Pair with `/reflect` for a complete loop: `/reflect` captures the lightweight retrospective signal; `/post-mortem` captures the engineering record. They serve different audiences. ## When to Skip - **Bug not fixed yet, or fix not validated.** A post-mortem of a hypothesis is misleading. Refuse and tell the user what's missing. …
Read the whole file at its exact version.
How to install
mdr add pitimon/8-habit-ai-dev/post-mortem@sha256:592ae5c1e027c6efThe line at the top of this page pins the label git:20260914.5d5e0e3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_r6kd5vx4tueb5g6l)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 8, 2026 and Sep 14, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.5d5e0e3 latest | 2026-09-14 | 5d5e0e3 | 13,405 B | A | view · diff |
| git:20260912.76bec51 | 2026-09-12 | 76bec51 | 13,323 B | A | view · diff |
| git:20260912.910e521 | 2026-09-12 | 910e521 | 13,402 B | A | view · diff |
| git:20260615.37b2504 | 2026-06-15 | 37b2504 | 13,271 B | A | view · diff |
| git:20260608.fa142bd | 2026-06-08 | fa142bd | 13,271 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13405 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pitimon/8-habit-ai-dev · 3 stars · license MIT · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r6kd5vx4tueb5g6l GET https://markdownregistry.com/api/v1/resolve?ref=pitimon/8-habit-ai-dev/post-mortem GET https://markdownregistry.com/api/v1/blob/592ae5c1e027c6eff468147534aca19e700754657c1ebf78d83bf774f3d2bd2a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from pitimon/8-habit-ai-dev
Every file in pitimon/8-habit-ai-dev