skills.rest
imbingox
imbingoxCOMMUNITY
Explore all skills by this author →
GitHub

trellis-break-loop

Analyze fixed bugs with a 5-dimensions framework and generate postmortem reports.

Updated Mar 25, 2026
Search Tags:#architecture#documentation#prevention#postmortem#analyze#root-cause#bug
One-click install
npx skills add https://github.com/imbingox/acex --skill trellis-break-loop-imbingox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-break-loop
Source: https://github.com/imbingox/acex/tree/main/.agents/skills/trellis-break-loop
Command: npx skills add https://github.com/imbingox/acex --skill trellis-break-loop-imbingox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to conduct deep post-analysis after a bug is fixed to break the cycle of fixes-forget-repeat by capturing root causes, prevention strategies, and knowledge into specs.

Core Features & Use Cases

  • Root Cause Analysis: Classify bug into categories and map propagation risks across layers.
  • Prevention & Knowledge Capture: Document prevention mechanisms and update specs and tickets.
  • Guided Reflections: Produce a formal postmortem narrative that informs future development and testing.
  • Use Case: After shipping a fix, run this skill to prevent regression by codifying the learnings into design docs and tests.

Quick Start

Analyze the just-fixed bug using the 5-dimensions framework and generate a structured postmortem report.

Frequently Asked Questions about trellis-break-loop

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

FAQPage Schema
How do I write a postmortem report after fixing a bug?▼

To write a postmortem report after a bug fix, identify the root-cause category and propagation risks, then apply a 5-dimensions framework to capture prevention mechanisms, design improvements, and testing gaps.

What is the best way to prevent recurring bugs in software architecture?▼

Preventing recurring bugs requires capturing root causes and prevention strategies into architecture documentation and specs, using a structured postmortem to break the cycle of fixes-forget-repeat.

How do I analyze root-cause categories and propagation risks across layers?▼

You analyze root-cause categories and map propagation risks across layers by conducting a deep post-analysis after the bug fix, documenting how failures propagate to inform future design improvements.

Can I update existing specs and tickets as part of a bug postmortem?▼

Yes, a bug postmortem can create or update related specs and tickets to codify learnings, ensuring prevention mechanisms and testing gaps are formally documented for future development.

When should I run a postmortem analysis to prevent regression?▼

You should run a postmortem analysis immediately after shipping a fix to prevent regression by applying a 5-dimensions framework that captures design improvements and testing gaps into documentation.

Related Skills

Explore More Software Engineering Skills→
AIBiz-AutomatyzacjeAIBiz-Automatyzacje
70

dev-compound

Document resolved software problems into a structured knowledge base.

Community
Advanced
ref-docsref-docs

bug-hunter

Reproduce software bugs, analyze causes, and generate fix plans.

Official
Advanced
KatsumitecKatsumitec

vibe-sdlc-dev

Automate issue tracking, code development, and testing for AI-first projects.

Official
Advanced
XiaSanwXiaSanw
2

trellis-break-loop

Analyze fixed bugs to identify root causes and generate prevention specs.

Community
Advanced