skills.rest
joshft
joshftCOMMUNITY
Explore all skills by this author →
GitHub

cpostmortem

Trace missed workflow phases and generate PMB records for post-merge bugs.

65|2|Updated Mar 27, 2026
Search Tags:#architecture#quality-assurance#postmortem#bug-analysis#workflow-improvement#antipattern
One-click install
npx skills add https://github.com/joshft/correctless --skill cpostmortem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cpostmortem
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/cpostmortem
Command: npx skills add https://github.com/joshft/correctless --skill cpostmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-merge bugs often slip through the development and review process, leaving production issues that are hard to trace. This Skill identifies where the workflow failed to catch the bug and documents a path to strengthen safeguards.

Core Features & Use Cases

  • Trace missed phases (spec, review, QA, audit, and verification) to determine where the bug bypassed checks.
  • Generate PMB entries, antipatterns, and corrective actions to codify lessons learned and prevent recurrence.
  • Maintain a formal postmortem record and learning that informs future Claude Code cycles and workflow improvements.

Quick Start

Trigger /cpostmortem after a production bug is found to begin the postmortem analysis.

Frequently Asked Questions about cpostmortem

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

FAQPage Schema
How do I analyze a post-merge bug to find where it escaped detection?▼

Post-merge bug analysis traces missed workflow phases like spec, review, QA, audit, and verification to determine exactly where the bug bypassed checks and slipped into production.

What is a postmortem record for production bugs and when do I need one?▼

A postmortem record documents why a production bug escaped detection, generating antipatterns and corrective actions to harden workflows and prevent recurrence. You need it after finding post-merge bugs.

How do I generate corrective actions and antipatterns after a workflow failure?▼

Generate corrective actions and antipatterns by applying postmortem analysis to the missed workflow phase, creating formal PMB records and architecture learning entries that codify lessons learned.

Can I use postmortem analysis to update phase-effectiveness and prevent bug recurrence?▼

Yes, postmortem analysis enforces PMB formatting and phase-effectiveness updates while generating architecture learnings and CLAUDE learnings to prevent future bug recurrence across development cycles.

Does post-merge bug analysis require any specific dependencies or components?▼

Post-merge bug analysis requires no external dependencies or components, operating entirely within the Correctless workflow to trace missed phases and generate corrective actions for production bugs.

Related Skills

Explore More Software Engineering Skills→
olaservoolaservo
10

comprehensive-issue-analyzer

Fetch all open GitHub issues via pagination and generate a triage report.

Community
Intermediate
OleksandrKucherenkoOleksandrKucherenko
16

skill-learning-patterns

Summarize task learnings into validated, PR-ready SKILL.md patterns.

Community
Advanced
joshftjoshft
65

ctdd

Coordinates RED, GREEN, and QA agents for discipline-driven TDD workflows.

Community
Advanced
RediSearchRediSearch
6.2k

run-rust-benchmarks

Run Rust benchmarks and compare performance against the C implementation.

Official
Advanced