skills.rest
SilentFlower
SilentFlowerCOMMUNITY
Explore all skills by this author →
GitHub

break-loop

Analyze resolved bugs with a five-dimensional framework and generate markdown reports.

Updated Apr 15, 2026
Search Tags:#debugging#specification#analysis#prevention#knowledge#root-cause#bug
One-click install
npx skills add https://github.com/SilentFlower/flower-cli --skill break-loop-silentflower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-loop
Source: https://github.com/SilentFlower/flower-cli/tree/main/.agents/skills/break-loop
Command: npx skills add https://github.com/SilentFlower/flower-cli --skill break-loop-silentflower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents the cycle of fixing bugs and then forgetting the underlying causes, ensuring that each resolved issue contributes to lasting improvements and avoids recurrence.

Core Features & Use Cases

  • Five‑dimensional analysis covering root cause categorization, fix failure reasons, prevention mechanisms, systematic expansion, and knowledge capture.
  • Actionable outcomes such as updates to project specification guides, creation of issue tickets, and documentation enhancements.
  • Use Case: After resolving a tricky bug that repeatedly appears, run this skill to produce a structured report and embed the lessons into the codebase's spec repository.

Quick Start

Run the break-loop skill immediately after a bug fix to generate a comprehensive analysis report.

Frequently Asked Questions about break-loop

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

FAQPage Schema
How do I analyze a resolved bug to prevent recurrence?▼

To analyze a resolved bug for recurrence prevention, apply a five-dimensional framework assessing cause category, fix failure reasons, prevention mechanisms, systematic impact, and knowledge capture to generate a structured markdown report.

What is the best way to document root-cause analysis after debugging?▼

The best way to document root-cause analysis after debugging is to capture the underlying causes by updating project specification guides and creating issue tickets, embedding learned insights directly into the codebase's spec repository.

How does a five-dimensional debugging framework work?▼

A five-dimensional debugging framework works by evaluating root cause categorization, fix failure reasons, prevention mechanisms, systematic expansion, and knowledge capture to transform temporary bug fixes into lasting project safeguards.

When do I need to generate a structured report after a bug fix?▼

You need to generate a structured report immediately after a tricky or repetitive bug fix to break the cycle of forgetting underlying causes and ensure the resolved issue contributes to lasting improvements.

Can I update project specification guides with debugging insights?▼

Yes, you can update project specification guides with debugging insights by running an analysis skill that embeds the learned lessons from a resolved issue directly into your codebase documentation.

Does this bug analysis approach require external dependencies?▼

No, this bug analysis approach requires no external dependencies, operating directly to produce comprehensive analysis reports and documentation enhancements for your development workflow.

Related Skills

Explore More Software Engineering Skills→
rory-datarory-data

debugging-dags

Diagnose failed Airflow DAGs and provide root-cause remediation.

Community
Advanced
imbingoximbingox

trellis-break-loop

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

Community
Advanced
RebornQRebornQ
52

trellis-break-loop

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

Community
Advanced
ZiphyrienZiphyrien
60

trellis-break-loop

Categorize root causes and capture preventive knowledge into specs after bug fixes.

Community
Advanced