skills.rest
TbK0ng
TbK0ngCOMMUNITY
Explore all skills by this author →
GitHub

break-loop

Diagnose bug root causes and generate structured prevention analyses.

Updated Feb 23, 2026
Search Tags:#debugging#code-quality#root-cause#process-improvement#bug-analysis#break-loop
One-click install
npx skills add https://github.com/TbK0ng/mytrellis --skill break-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-loop
Source: https://github.com/TbK0ng/mytrellis/tree/main/.agents/skills/break-loop
Command: npx skills add https://github.com/TbK0ng/mytrellis --skill break-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break the Loop - Deep Bug Analysis helps teams understand why a bug recurs after fixes and provides a structured approach to stop repeating failures.

Core Features & Use Cases

  • Root-cause classification: identifies whether issues stem from missing specifications, cross-layer contracts, change propagation, test gaps, or implicit assumptions.
  • Structured analysis framework: guides investigation across five dimensions: root-cause category, failed fixes, prevention mechanisms, broader systemic implications, and knowledge capture.
  • Knowledge capture & artifact generation: creates actionable outputs and templates to prevent future regressions, including documentation updates and issue tickets.

Quick Start

Analyze a recently fixed bug by running the Break the Loop analysis on the failing test case.

Frequently Asked Questions about break-loop

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

FAQPage Schema
How do I find the root cause of a recurring bug after a failed fix?▼

Root-cause analysis identifies why a bug recurs by classifying issues across missing specifications, cross-layer contracts, change propagation, test gaps, or implicit assumptions to prevent future regressions.

What is the best way to structure a post-fix review for code and tests?▼

A structured post-fix review evaluates five dimensions: root-cause category, failed fixes, prevention mechanisms, broader systemic implications, and knowledge capture to ensure comprehensive bug analysis.

How do I create a bug analysis template to prevent regressions?▼

Generate a bug analysis template by documenting root-cause categorization, prevention mechanisms, and knowledge capture to produce actionable artifacts like documentation updates and issue tickets.

Why do implicit assumptions cause bugs to repeat after deployment?▼

Implicit assumptions cause repeating bugs when cross-layer contracts and change propagation fail, requiring structured post-fix reviews to surface these hidden root causes and enforce preventive measures.

Can I use this analysis on failing test cases across configurations?▼

Yes, you can apply this analysis during post-fix reviews across code, tests, and configurations to diagnose root causes and produce structured, actionable analyses to prevent recurrence.

What should I do to capture knowledge after diagnosing a bug?▼

Capture knowledge by generating actionable outputs and templates from the bug analysis, including documentation updates and issue tickets, to prevent future regressions and failed fixes.

Related Skills

Explore More Software Engineering Skills→
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
mmbianco78mmbianco78

kaizen

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

Community
Basic
ybbms777ybbms777
1

testing-reviewer

Identifies test quality gaps and false confidence risks in code diffs.

Community
Intermediate
eng-vmessiaheng-vmessiah
2

ai-regression-testing

Automate regression tests validating API response shapes and state integrity.

Community
Intermediate