trellis-break-loop
Skill301 starsChanged 6 months agoMITView on GitHub
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.
21 other projects use a version of this, 19 of them edited.
Adopted by
Most recently taken up by
- phoben/agent-skillsedited, first seen Nov 8, 2026
- vibex-ai/vibexedited, first seen Nov 8, 2026
- mipawn/cc-useedited, first seen Nov 1, 2026
- deequoique/stashseekedited, first seen Oct 20, 2026
- tmdy/CodeDeckedited, first seen Oct 18, 2026
- zhexin233-ui/easytoagentsedited, first seen Oct 11, 2026
Used with
Projects with it also use trellis-channel, trellis-session-insight and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
wayfarer35Skilltrellis-channel
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
Also in 18 projects that use this
- wayfarer35Skill
trellis-session-insight
Reach into past AI conversation history through the `trellis mem` CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work, debugging a familiar bug, continuing a task across sessions, or doing a finish-work review. Returns raw past dialogue; decide for the moment whether to update spec, append to task notes, quote inline in the answer, or just internalize.
Also in 18 projects that use this
- +1 more from wayfarer35
Other versions21 projects use a version of this.
Word for word · 2
- mumu-0922/GankAIGC★ 396100% same
- linyimin0812/folyn★ 41100% same
Edited · 19
- mindfold-ai/Trellis★ 15k67% same
- EcoPasteHub/EcoPaste★ 7.5k67% same
- QiaoKes/fntv-electron★ 1.3k67% same
- CharTyr/STS2-Agent★ 35767% same
- hsingjui/ContextWeaver★ 29567% same
- fy-agent/fyagent★ 21867% same
- vibex-ai/vibex★ 7067% same
- deequoique/stashseek★ 5867% same
- mipawn/cc-use★ 967% same
- xhl592576605/agent-skills-mesh★ 867% same
9 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- trellis-before-devSkill
- trellis-brainstormSkill
- trellis-checkSkill
- trellis-continueSkill
- trellis-finish-workSkill
- trellis-metaSkill
- trellis-spec-bootstarpSkill
- trellis-startSkill
- trellis-update-specSkill
The file
We split this skill into the rules it gives an agent
9 rules. 4 are common, 0 are distinctive, and 5 are very specific to this project.
4
Common
Most of the 19 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 8
When debug is complete, use this for deep analysis to break the "fix bug -> forget -> repeat" cycle.
- Common: line 30
If you tried multiple fixes before succeeding, analyze each failure:
- Common: line 118
IMPORTANT: After completing the analysis above, you MUST immediately:
- Common: line 120
Update spec/guides: - Don't just list TODOs, actually update the relevant files:
- Very specific: line 121
If it's a cross-platform issue → update cross-platform-thinking-guide.md
- Very specific: line 122
If it's a cross-layer issue → update cross-layer-thinking-guide.md
- Very specific: line 123
If it's a code reuse issue → update code-reuse-thinking-guide.md
- Very specific: line 124
If it's domain-specific → update backend/*.md or frontend/*.md
- Very specific: line 126
Sync templates: - After updating .trellis/spec/, sync to src/templates/markdown/spec/
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Tool Limitation: grep missed it, type check wasn't strict
- Mental Model: Kept looking in same layer, didn't think cross-layer
3. Prevention Mechanisms
What mechanisms would prevent this from happening again?
| Type | Description | Example |
| Documentation | Write it down so people know | Update thinking guide |
| Architecture | Make the error impossible structurally | Type-safe wrappers |
| Compile-time | Strict type checking, no escape hatches | Signature change causes compile error |
| Runtime | Monitoring, alerts, scans | Detect orphan entities |
| Test Coverage | E2E tests, integration tests | Verify full flow |
| Code Review | Checklist, PR template | "Did you check X?" |
4. Systematic Expansion
What broader problems does this bug reveal?
- Similar Issues: Where else might this problem exist?
- Design Flaw: Is there a fundamental architecture issue?
- Process Flaw: Is there a development process improvement?
- Knowledge Gap: Is the team missing some understanding?
5. Knowledge Capture
Solidify insights into the system:
- Update
.trellis/spec/guides/thinking guides - Update relevant
.trellis/spec/docs - Create issue record (if applicable)
- Create feature ticket for root fix
- Update check guidelines if needed
Output Format
Please output analysis in this format:
## Bug Analysis: [Short Description]
### 1. Root Cause Category
- **Category**: [A/B/C/D/E] - [Category Name]
- **Specific Cause**: [Detailed description]
### 2. Why Fixes Failed (if applicable)
1. [First attempt]: [Why it failed]
2. [Second attempt]: [Why it failed]
...
### 3. Prevention Mechanisms
| Priority | Mechanism | Specific Action | Status |
|----------|-----------|-----------------|--------|
| P0 | ... | ... | TODO/DONE |
### 4. Systematic Expansion
- **Similar Issues**: [List places with similar problems]
- **Design Improvement**: [Architecture-level suggestions]
- **Process Improvement**: [Development process suggestions]
### 5. Knowledge Capture
- [ ] [Documents to update / tickets to create]Core Philosophy
The value of debugging is not in fixing the bug, but in making this class of bugs never happen again.
Three levels of insight:
- Tactical: How to fix THIS bug
- Strategic: How to prevent THIS CLASS of bugs
- Philosophical: How to expand thinking patterns
30 minutes of analysis saves 30 hours of future debugging.
After Analysis: Immediate Actions
IMPORTANT: After completing the analysis above, you MUST immediately:
- Update spec/guides - Don't just list TODOs, actually update the relevant files:
- If it's a cross-platform issue → update
cross-platform-thinking-guide.md - If it's a cross-layer issue → update
cross-layer-thinking-guide.md - If it's a code reuse issue → update
code-reuse-thinking-guide.md - If it's domain-specific → update
backend/*.mdorfrontend/*.md
- If it's a cross-platform issue → update
- Sync templates - After updating
.trellis/spec/, sync tosrc/templates/markdown/spec/ - Commit the spec updates - This is the primary output, not just the analysis text
The analysis is worthless if it stays in chat. The value is in the updated specs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.