skills.rest
yanzhangshuai
yanzhangshuaiCOMMUNITY
Explore all skills by this author →
GitHub

break-loop

Conduct structured post-mortems to identify root causes of bugs.

Updated Mar 3, 2026
Search Tags:#debugging#prevention#quality-assurance#postmortem#software-engineering#root-cause-analysis
One-click install
npx skills add https://github.com/yanzhangshuai/wen-yuan --skill break-loop-yanzhangshuai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-loop
Source: https://github.com/yanzhangshuai/wen-yuan/tree/main/.agents/skills/break-loop
Command: npx skills add https://github.com/yanzhangshuai/wen-yuan --skill break-loop-yanzhangshuai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break the loop of "fix bug → forget → repeat" by conducting a structured post-mortem that uncovers root causes and improvement opportunities.

Core Features & Use Cases

  • Root-cause categorization across common defect classes
  • Structured prevention recommendations and process improvements
  • Knowledge capture to prevent regression in future fixes

Quick Start

Conduct a post-mortem analysis to break the fix-bug-forget-repeat loop after a bug is fixed.

Frequently Asked Questions about break-loop

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

FAQPage Schema
How do I conduct a root cause analysis to stop recurring software bugs?▼

Root cause analysis for recurring software bugs requires a structured post-mortem framework that categorizes defect classes, recommends prevention mechanisms, and captures knowledge to prevent regression in future fixes.

What is the best way to structure a bug postmortem for software engineering?▼

A structured bug postmortem identifies root causes across common defect classes, applies prevention recommendations for process improvements, and uses knowledge capture prompts to break the fix-forget-repeat cycle.

How do I prevent the fix bug forget repeat cycle in my debugging workflow?▼

Preventing the fix bug forget repeat cycle involves applying structured post-mortem analysis after fixes to uncover root causes, implement prevention mechanisms, and capture regression knowledge across code changes and deployment pipelines.

Can I apply postmortem analysis across code changes, tests, and deployment pipelines?▼

Yes, structured postmortem analysis applies directly to debugging workflows across code changes, tests, and deployment pipelines to identify root causes and capture prevention knowledge for future quality assurance.

What categories of root causes should I look for during deep bug analysis?▼

Deep bug analysis uses a structured framework with root-cause categories covering common defect classes to identify underlying issues, recommend process improvements, and capture knowledge to prevent regression.

Related Skills

Explore More Software Engineering Skills→
glowingkittyglowingkitty
43

openmates:fix-tests

Triage failing test runs into root-cause groups and apply targeted fixes.

Community
Intermediate
robit-manrobit-man

regression-report

Generate regression analysis reports from bisect, baseline, and metrics data.

Community
Advanced
RheasilviaRheasilvia

Review Changes

Analyze code changes for risk and test coverage via knowledge graph.

Community
Advanced
haolangehaolange
15

capture-repro

Creates deterministic capture baselines and environment snapshots for runtime debugging.

Community
Advanced