trellis-break-loop
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
Best for post-mortem debuggingWorks with GitHubLow risk
⌘source
- author
@mindfold-ai- language
- TypeScript
★6.7kstars
366forks
Apr 30, 2026
✦overview.md
Key Features
- ·5-dimension root cause analysis
- ·Failed fix pattern analysis
- ·Prevention mechanism specification
- ·Knowledge capture into specs
Use Cases
- →After fixing a bug, analyze root cause to prevent recurrence
- →Reviewing a series of failed fixes to find pattern
- →Creating spec documentation from bug analysis insights
Best for
- ✓post-mortem debugging
- ✓bug prevention
- ✓development teams
Not ideal for
- !one-off quick fixes
- !emergency hotfixes
FAQs
name
trellis-break-loop
description
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
Break the Loop - Deep Bug Analysis
When debug is complete, use this for deep analysis to break the "fix bug -> forget -> repeat" cycle.
Analysis Framework
Analyze the bug you just fixed from these 5 dimensions:
1. Root Cause Category
Which category does this bug belong to?
| Category | Characteristics | Example |
|---|---|---|
| A. Missing Spec | No documentation on how to do it | New feature without checklist |
| B. Cross-Layer Contract | Interface between layers unclear | API returns different format than expected |
| C. Change Propagation Failure | Changed one place, missed others | Changed function signature, missed call sites |
| D. Test Coverage Gap | Unit test passes, integration fails | Works alone, breaks when combined |
| E. Implicit Assumption | Code relies on undocumented assumption | Timestamp seconds vs milliseconds |
2. Why Fixes Failed (if applicable)
If you tried multiple fixes before succeeding, analyze each failure:
- Surface Fix: Fixed symptom, not root cause
- Incomplete Scope: Found root cause, didn't cover all cases
$install
1-click copynpx skills add mindfold-ai/Trellis --skill trellis-break-loopSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.