break-loop

Generate structured post-mortems with root causes, failure modes, and prevention steps.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/BaSui01/agentflow --skill break-loop-basui01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: break-loop
Source: https://github.com/BaSui01/agentflow/tree/main/.agents/skills/break-loop
Command: npx skills add https://github.com/BaSui01/agentflow --skill break-loop-basui01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break-loop provides a structured post-mortem framework to analyze bugs after a fix, capturing root causes, failure modes, prevention strategies, and knowledge for future prevention.

Core Features & Use Cases

  • Five-dimension analysis framework for comprehensive bug review
  • Guides documentation updates and lessons learned for project guides and thinking materials
  • Outputs a structured post-mortem suitable for knowledge bases, PR reviews, and team reviews
  • Use when debugging completes, when the same class of bugs recurs, or when you want to capture debugging insights into project documentation

Quick Start

After completing a debugging session, generate a structured break-loop post-mortem and update project documentation with lessons learned.

Frequently Asked Questions about break-loop

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

FAQPage Schema
How do I write a structured post-mortem after fixing a bug?

A structured post-mortem identifies root cause categories, failure modes, and prevention steps after debugging. Apply a five-dimension framework to capture debugging insights and update project documentation to prevent recurrence.

What is the best way to prevent recurring bug classes in software development?

To prevent recurring bugs, generate a structured post-mortem after a fix to identify root causes and failure modes. Applying explicit knowledge-capture actions updates project guides and breaks the cycle of recurring issues.

How do I document root-cause analysis results for team reviews and knowledge bases?

Document root-cause analysis by outputting structured post-mortem findings suitable for knowledge bases and PR reviews. Guide thinking materials and documentation updates to capture lessons learned from the debugging session.

Can I use a post-mortem framework for any software debugging workflow?

Yes, apply this post-mortem framework to software development workflows requiring structured analysis after debugging completes. It supports identifying root cause categories and prevention steps across various debugging contexts.

Why do I need a five-dimension framework for bug analysis?

A five-dimension framework provides comprehensive bug review by analyzing root causes, failure modes, and prevention strategies. This structured approach ensures explicit knowledge-capture actions break the cycle of recurring bugs.

When should I generate a bug analysis post-mortem in my development cycle?

Generate a post-mortem when debugging completes, when the same class of bugs recurs, or when capturing debugging insights into project documentation. This ensures lessons learned are systematically integrated into knowledge bases.