systematic-debugging

仓库创建 2026年3月12日最近提交 23 天前SkillHot 收录 22 天前

▸ 精选理由

防止盲目试错，节省调试时间并降低回归风险。

这个 Skill 做什么

遇到 bug 时强制进行根因分析再修复，避免仓促补丁掩盖问题。

遇到 bug 或测试失败时先别急着打补丁，先把根本原因扒清楚再修。适合在时间紧、修复看起来“显而易见”、或已尝试过但没解决时使用。特别之处是把“先找根因再修复”当成硬规则，避免快速修补掩盖更深层的问题。

▸ 展开 SKILL.md 英文原文

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. ESPECIALLY when under time pressure, when fix seems 'obvious', or after 1+ failed fix attempts. Also trigger when catching yourself thinking 'let me just try this quick fix'.

开发编程系统化调试根因分析修复规范通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/huanlongAI/tzh-Harness/main/cowork-skills/systematic-debugging/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/huanlongAI/tzh-Harness/main/cowork-skills/systematic-debugging/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Systematic Debugging

## Overview

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure.

**Violating the letter of this process is violating the spirit of debugging.**

## The Iron Law

```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```

If you haven't completed Phase 1, you cannot propose fixes.

## When to Use

Use for ANY technical issue:
- Test failures
- Bugs in production
- Unexpected behavior
- Performance problems
- Build failures
- Integration issues

**Use this ESPECIALLY when:**
- Under time pressure (emergencies make guessing tempting)
- "Just one q

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有