Skill

postmortem

Structured bug autopsy after fixing a bug. Analyzes root cause, classifies the bug, and recommends prevention. Run after any non-trivial bug fix.

Install

npx claudepluginhub artmin96/forge-studio --plugin evaluator

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.8k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-editorial-review-prose

Reviews prose for communication issues impeding comprehension, outputs minimal fixes in a three-column table per Microsoft Writing Style Guide. Useful for 'review prose' or 'improve prose' requests.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Process

1. What Happened

Describe the bug behavior in one sentence. What did the user see? What was expected?

2. Root Cause

Explain WHY it happened — not just what you changed to fix it. Trace the chain:

What was the immediate cause?

What allowed that cause to exist?

Was there a deeper design issue?

3. Category

Classify the bug. Pick one:

State management — stale state, race condition, missing sync

Type mismatch — wrong type, missing null check at system boundary

Boundary error — off-by-one, empty input, overflow

Logic error — wrong conditional, missing branch, inverted check

Integration — API contract changed, schema mismatch, version drift

Configuration — wrong env var, missing config, path issue

Concurrency — deadlock, race condition, ordering assumption

4. Could It Have Been Caught Earlier?

Was there a missing test? Write it now.

Was there a missing type? Add it.

Was there a missing validation at a system boundary? Add it.

Would a linter rule have caught it? Note which one.

5. Prevention

One concrete recommendation. Not vague ("be more careful") — specific:

"Add integration test for X endpoint with empty payload"

"Add runtime type guard at API boundary for field Y"

"Enable ESLint rule no-floating-promises"

Postmortem: Bug Autopsy

Run this after fixing a bug. Don't just fix and move on — every bug is a potential guardrail.