ante-mortem

Writes fictional post-mortem reports for plausible future bugs in production code.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill ante-mortem-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ante-mortem
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/ante-mortem
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill ante-mortem-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases contain hidden fragilities—implicit assumptions, shared mutable state, invisible invariants—that only surface when a future developer makes a reasonable edit. This Skill identifies those fragile patterns before they break by writing realistic incident reports for bugs that haven't happened yet. ## Core Features & Use Cases - Fragility Detection: Reads code deeply and matches it against an 11-pattern catalogue covering ordering dependencies, stringly-typed contracts, coincidental correctness, security fragility, and more. - Fictional Post-Mortems: Produces concrete, past-tense incident reports in ANTE-MORTEM.md naming actual functions, variables, and plausible future edits. - Hardening TODOs: Extracts actionable suggestions into TODOS.md tagged as [CHORE], [INVESTIGATE], [SECURITY], or [BUG] for real defects found during analysis. - Use Case: Before a major refactor, run the Skill on a core module to surface architectural assumptions that could silently break, then hand the generated TODOs to the team as a hardening backlog. ## Quick Start Ask the AI to run an ante-mortem analysis on a specific module or directory to generate fictional post-mortems and hardening TODOs.

Frequently Asked Questions about ante-mortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find fragile code before it breaks?▼

Run an ante-mortem analysis that reads production code deeply and matches it against fragility patterns like implicit ordering, shared mutable state, and invisible invariants. The output is a set of fictional post-mortems describing plausible future failures plus hardening TODOs.

What is an ante-mortem in software engineering?▼

An ante-mortem is a proactive incident report written before a bug occurs. It imagines a reasonable future edit, describes how it would break the code, and suggests hardening steps, complementing traditional post-mortems written after real incidents.

How is ante-mortem different from a code review or bug hunt?▼

Ante-mortem targets fragility against future edits, not current correctness. The code may work perfectly today; the analysis asks what plausible change a well-intentioned developer could make that would break it non-obviously.

What happens when a real bug is found during ante-mortem analysis?▼

Real bugs are flagged immediately as plain text output and recorded as [BUG] TODOs in TODOS.md rather than buried in fictional post-mortems. Security fragilities get [SECURITY] tags with a suggestion to run a deeper security audit.

What are the limitations of ante-mortem analysis?▼

It does not fix code, only reports fragility and writes TODOs. It avoids adversarial or extremely unlikely scenarios, so it complements rather than replaces testing, fuzzing, and security auditing.