skills.rest
yizhitangtongxue
yizhitangtongxueCOMMUNITY
Explore all skills by this author →
GitHub

break-loop

Analyzes fixed bugs across five dimensions to prevent recurring defect patterns.

Updated Mar 24, 2026
Search Tags:#code quality#debugging#documentation#bug prevention#root cause analysis#knowledge capture#postmortem
One-click install
npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill break-loop-yizhitangtongxue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-loop
Source: https://github.com/yizhitangtongxue/opencode-switch/tree/main/.agents/skills/break-loop
Command: npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill break-loop-yizhitangtongxue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After fixing a bug, teams often move on without understanding why it happened, leading to the same class of bugs recurring. This Skill structures a post-debug deep analysis that converts a one-off fix into permanent prevention mechanisms and updated documentation. ## Core Features & Use Cases - Five-Dimension Analysis Framework: Categorizes root causes (missing spec, cross-layer contract, change propagation, test coverage gap, implicit assumption), reviews failed fix attempts, and designs prevention mechanisms. - Structured Output Template: Produces a standardized Markdown analysis report with prioritized prevention actions (P0/P1) and knowledge capture checklists. - Spec-Driven Follow-Through: Mandates immediate updates to thinking guides and spec documents, syncing templates and committing changes so insights persist beyond the chat. - Use Case: After spending hours fixing a timestamp unit mismatch between frontend and backend, run this analysis to classify it as an implicit assumption bug, identify similar risks elsewhere, and update the cross-layer thinking guide. ## Quick Start Ask the AI to run the break-loop analysis on the bug you just fixed and update the relevant spec guides.

Frequently Asked Questions about break-loop

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

FAQPage Schema
How do I prevent the same bug from happening again after fixing it?▼

Run a structured post-fix analysis that classifies the root cause, reviews why earlier fix attempts failed, and defines prevention mechanisms such as documentation, type safety, tests, or monitoring. Then update your project's spec guides so the insight persists.

What is a root cause analysis framework for software bugs?▼

This framework uses five categories: missing spec, cross-layer contract mismatch, change propagation failure, test coverage gap, and implicit assumption. Classifying a bug into one category guides which prevention mechanism, such as documentation or compile-time checks, will actually stop recurrence.

When should I run a post-debug deep analysis?▼

Run it immediately after completing a debug session, especially when the fix required multiple attempts or revealed cross-layer issues. The analysis is most valuable while the debugging context is still fresh.

What are the limitations of post-fix bug analysis?▼

The analysis only adds value if its outputs are actually committed to documentation and specs; insights left in chat are lost. It also depends on the quality of the debugging session that preceded it and cannot fix underlying process issues by itself.

How do I turn a bug fix into documentation updates?▼

Map the bug's root cause to the relevant thinking guide, such as cross-platform or cross-layer guides, edit those files directly, sync any template copies, and commit the spec changes as the primary deliverable of the analysis.

Related Skills

Explore More Software Engineering Skills→
siviter-xyzsiviter-xyz
21

debugging

Diagnose software defects through structured root-cause analysis and hypothesis testing.

Official
Basic
SDDKKKSDDKKK

break-loop

Analyze fixed bugs with a five-dimensional framework and update .trellis/spec guides.

Community
Intermediate
apacheapache
79

magpie-issue-deduplicate

Identify and merge duplicate issues in issue trackers with maintainer confirmation.

Official
Intermediate
rabbicserabbicse

quality-postmortem

Analyze escaped defects and test suite health with 5 Whys analysis.

Community
Advanced