diagnosing-bugs

仓库创建 2026年7月6日最近提交 22 天前SkillHot 收录 22 天前

▸ 精选理由

强调建立快速反馈回路和分阶段排查，适合复杂问题处理。

这个 Skill 做什么

有结构化的诊断循环，用于定位难查 bug 与性能回归。

把难查的 bug 或性能回归拆成有序的诊断循环：先建立可靠的通过/失败反馈信号，再逐步缩小范围、复现并验证假设。适合有人说“帮我诊断”或系统报错、抛异常、变慢时使用，避免盲目改动。强调先读 CONTEXT.md、查看 ADRs，并保持紧密反馈回路作为诊断核心。

▸ 展开 SKILL.md 英文原文

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

开发编程缺陷定位性能回归诊断流程通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/K3639284/skills/main/skills/engineering/diagnosing-bugs/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/K3639284/skills/main/skills/engineering/diagnosing-bugs/SKILL.md"

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

# Diagnosing Bugs

A discipline for hard bugs. Skip phases only when explicitly justified.

When exploring the codebase, read `CONTEXT.md` (if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.

## Phase 1 — Build a feedback loop

**This is the skill.** Everything else is mechanical. If you have a **tight** pass/fail signal for the bug — one that goes red on _this_ bug — you will find the cause; bisection, hypothesis-testing, and instrumentation all just consume it. If you don't have one, no amount of staring at code will save you.

Spend disproportionate effort here. **Be aggressive. Be creative. Refuse to give up.**

### Ways to cons

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