debugging-rules
Debug from evidence and root cause through hypothesis, fix and verification; stop repeated speculative fixes.
- License 许可
- MIT
- 所属仓库
- 1aGh/maude
- 最近更新
- 2026-11-13
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- debugging-rules
- description
- Debug from evidence and root cause through hypothesis, fix and verification; stop repeated speculative fixes.
- user-invocable
- false
02 资源文件 12
- 参考文档_guide-00-overview.md529 B
- 参考文档_guide-01-iron-law.md261 B
- 参考文档_guide-02-when-to-apply.md881 B
- 参考文档_guide-03-four-phases.md4.5 KB
- 参考文档_guide-04-integration-with-the-workflow.md689 B
- 参考文档_guide-05-red-flags-stop-and-follow-process.md710 B
- 参考文档_guide-06-user-signals-you-re-doing-it-wrong.md497 B
- 参考文档_guide-07-common-rationalizations.md849 B
- 参考文档_guide-08-when-investigation-reveals-no-root-cause.md538 B
- 参考文档_guide-09-quick-reference.md471 B
- 参考文档_guide-10-real-world-impact.md242 B
- 参考文档_guide-11-related.md360 B
03 SKILL.md 正文
debugging-rules
Follow host conventions for Claude Code or Codex.
Find root cause before fixing. Gather evidence, reproduce, compare working paths, test a concrete hypothesis, then make and verify the smallest justified fix. Follow the four-phase procedure; repeated failed fixes trigger the architectural stop instead of another guess. Do not claim success without verification or mistake environmental evidence for product behavior.
Read only the relevant procedure
The references below retain the complete procedure. Read the entry for the stage before performing it; conditional examples, setup and troubleshooting load only when needed. A staged workflow follows its applicable stages in order, including verification and close-out. References to another section mean the matching row here, not permission to skip that requirement. Do not read all references at once.
| When | Read |
|---|---|
| Initial orientation, prerequisites and scope | Overview |
| When performing this stage: Iron Law | Iron Law |
| When performing this stage: When to apply | When to apply |
| For every debugging investigation | Four phases |
| When performing this stage: Integration with the workflow | Integration with the workflow |
| When performing this stage: Red flags — STOP and follow process | Red flags — STOP and follow process |
| When performing this stage: User signals you're doing it wrong | User signals you're doing it wrong |
| When performing this stage: Common rationalizations | Common rationalizations |
| When performing this stage: When investigation reveals "no root cause" | When investigation reveals "no root cause" |
| When performing this stage: Quick reference | Quick reference |
| When performing this stage: Real-world impact | Real-world impact |
| When performing this stage: Related | Related |
04 同仓库更多 Skills
workflow-state
Read and update workflow state when planning, executing, completing, pausing or resuming project work.
ui-rules
UI hard-stop rules and audit method: WCAG 2.1 AA accessibility, responsive layout and motion.
testing-rules
Apply test quality rules during implementation and review: meaningful assertions, isolation and coverage.
security-rules
Apply application and AI security checks to code reviews, implementation and threat-driven validation.
scenario
Author or run cross-platform UI scenarios with selectors, screenshots, platform coverage and result reports.
question-protocol
Batch necessary questions from workflow participants, collect user answers and route them to the requester.