skills.rest
LinnkidChen
LinnkidChenCOMMUNITY
Explore all skills by this author →
GitHub

break-loop

Document root causes and preventive measures after debugging sessions.

4|1|Updated Aug 9, 2025
Search Tags:#debugging#documentation#post-mortem#root-cause#process-improvement#knowledge-capture
One-click install
npx skills add https://github.com/LinnkidChen/Stock-Tracker --skill break-loop-linnkidchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-loop
Source: https://github.com/LinnkidChen/Stock-Tracker/tree/main/.agents/skills/break-loop
Command: npx skills add https://github.com/LinnkidChen/Stock-Tracker --skill break-loop-linnkidchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep post-fix bug analysis across five dimensions to break the cycle of fixing bugs without capturing lessons and preventing recurrence.

Core Features & Use Cases

  • Root-cause categorization to classify the primary fault.
  • Why fixes failed analysis to capture missed opportunities.
  • Prevention mechanisms to codify lessons into processes and docs.
  • Systematic expansion to reveal broader design or process gaps.
  • Knowledge capture to update guides and create traceable records.

Quick Start

Provide a structured post-mortem by following the five-dimension framework after a debugging session.

Frequently Asked Questions about break-loop

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

FAQPage Schema
How do I document a post-mortem after fixing a bug to prevent recurrence?▼

A post-mortem after fixing a bug requires identifying and documenting root causes and preventive measures. You apply a structured framework to capture lessons, propagate fixes, and create a traceable record to prevent recurring bugs.

What is root-cause analysis in post-fix debugging sessions?▼

Root-cause analysis in post-fix debugging is the process of categorizing the primary fault and capturing missed opportunities. It classifies why fixes failed previously to codify lessons into processes and documentation for future improvement.

How do I create a traceable post-mortem record for process improvement?▼

To create a traceable post-mortem record for process improvement, you capture knowledge in trellis/spec/ and related docs. This updates thinking guides and documents prevention mechanisms after your debugging session concludes.

Does post-fix bug analysis work across different codebases?▼

Yes, post-fix bug analysis applies to post-fix sessions across codebases. It systematically expands to reveal broader design or process gaps, ensuring knowledge capture and preventive measures are propagated regardless of the project.

What is the best way to analyze why a previous fix failed during debugging?▼

The best way to analyze why a fix failed is applying a five-dimension framework for deep post-fix bug analysis. This approach captures missed opportunities, categorizes the root cause, and codifies prevention mechanisms into your workflow.

When do I need to perform a post-fix bug analysis?▼

You need to perform a post-fix bug analysis immediately after a debugging session to break the cycle of fixing bugs without capturing lessons. It is required to update thinking guides and create traceable post-mortem records.

Related Skills

Explore More Software Engineering Skills→
steadyfallsteadyfall

gstack-openclaw-investigate

Diagnose software defects through structured root-cause investigation workflows.

Community
Advanced
SDDKKKSDDKKK

break-loop

Analyze fixed bugs with a five-dimensional framework and update .trellis/spec guides.

Community
Intermediate
RebornQRebornQ
52

trellis-break-loop

Generate reusable specifications from root-cause analysis after bug fixes.

Community
Advanced
mmbianco78mmbianco78

kaizen

Automate post-incident retrospectives with 5 Whys and PDCA cycles.

Community
Basic