skills.rest
nhouseholder
nhouseholderCOMMUNITY
Explore all skills by this author →
GitHub

root-cause-reflection

Identify flawed assumptions and reasoning gaps after significant bug fixes.

Updated Aug 23, 2026
Search Tags:#anti-patterns#learning#reflection#postmortem#root-cause#bug-fix#reasoning-chain
One-click install
npx skills add https://github.com/nhouseholder/nicks-claude-code-superpowers --skill root-cause-reflection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: root-cause-reflection
Source: https://github.com/nhouseholder/nicks-claude-code-superpowers/tree/main/skills/root-cause-reflection
Command: npx skills add https://github.com/nhouseholder/nicks-claude-code-superpowers --skill root-cause-reflection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After fixing a significant bug, analyze not only what broke but why your reasoning led to the bug. This skill records what went wrong, why the thinking was flawed, and how to think better next time, enabling continuous coder improvement.

Core Features & Use Cases

  • Post-bug-fix reflection that identifies flawed assumptions, missing checks, and reasoning gaps.
  • Trace the reasoning chain from issue to decision to root cause.
  • Extract concrete lessons and persist them for future avoidance of similar mistakes.

Quick Start

After a non-trivial bug fix, run the Reflection Protocol to capture the root cause and actionable lessons for future fixes.

Frequently Asked Questions about root-cause-reflection

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

FAQPage Schema
How do I trace the root cause of a bug after fixing it?▼

Post-bug reflection identifies flawed assumptions and reasoning gaps by tracing the decision chain from issue to root cause. This process extracts concrete lessons to prevent repeating similar mistakes across codebases, QA incidents, and design defects.

What is the best way to document flawed assumptions after a software incident?▼

Documenting flawed assumptions after a software incident involves recording what went wrong, why the thinking was flawed, and how to think better next time. This captures root causes and persists actionable lessons for continuous improvement.

How do I extract actionable lessons from a postmortem review?▼

Extract actionable lessons from a postmortem review by applying a structured Reflection Protocol that identifies missing checks, traces the reasoning chain, and persists insights to avoid similar design defects and bugs in the future.

Can I use root cause reflection for QA incidents and design defects?▼

Yes, you can use root cause reflection for QA incidents and design defects. The analysis applies to post-fix reviews across codebases to identify reasoning gaps and extract lessons regardless of the defect origin.

When should I perform a post-bug-fix reflection?▼

Perform a post-bug-fix reflection after resolving a non-trivial bug. Applying the analysis to significant fixes ensures you capture deep reasoning gaps and flawed assumptions rather than superficial syntax errors.

Related Skills

Explore More Software Engineering Skills→
mraakashshahmraakashshah
5

documenting-solutions

Document resolved technical issues with symptoms, root causes, and prevention guidance.

Community
Basic
mccode415mccode415

reflection

Analyze past AI sessions to identify root causes and generate actionable recommendations.

Community
Advanced
imbingoximbingox

trellis-break-loop

Analyze fixed bugs with a 5-dimensions framework and generate postmortem reports.

Community
Advanced
8GG-Git8GG-Git

incident-response

Manages production incidents from detection to blameless postmortem review.

Community
Intermediate