trellis-break-loop

深度缺陷分析，打破「修了又忘、反复踩坑」：根因分类、失败修复复盘与预防机制。

核心说明

以下为上游 SKILL.md 摘要（英文原文结构保留要点）：

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, integr

安装

随 Trellis 一并分发。执行 trellis init 后可在 .agents/skills/trellis-break-loop/（及各平台 skill 目录）使用。

npm install -g @mindfoldhq/trellis@latest
trellis init -u your-name

来源：mindfold-ai/Trellis · .agents/skills/trellis-break-loop