Systematic Debugging

Systematic Debugging is a Quality skill for Claude Code, published by jnMetaCode in superpowers-zh.

7.7K stars729 forkson jnMetaCode/superpowers-zhAdded 2026/08/15Repository updated 2026/08/12

agent-skillsagentic-codingai-codingchineseclaude-codecode-reviewcursorgemini-clikiromcpnpm-packageprompt-engineeringskillssuperpowerstddtrae

Install in seconds

Install Systematic Debugging

Copy Systematic Debugging into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/systematic-debugging ~/.claude/skills/systematic-debugging

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/jnMetaCode/superpowers-zh.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/systematic-debugging/SKILL.md in jnMetaCode/superpowers-zh
Installs to: ~/.claude/skills/systematic-debugging
Collection: One of 20 skills cataloged from this repository
Category: Quality — 1354 skills

What Systematic Debugging does

Systematic Debugging guides a rigorous four-phase process to find root causes before attempting fixes. Use it for test failures, production bugs, performance issues, or any unexpected behavior.

Systematic Debugging is cataloged under Quality on DirSkills. Systematic Debugging comes from a repository tagged agent-skills, agentic-coding, ai-coding, chinese and claude-code.

Documentation

README

Excerpt

不做根因调查，不许提修复方案

如果你还没完成第一阶段，就不能提出修复方案。

何时使用

用于任何技术问题：

测试失败
生产环境 bug
异常行为
性能问题
构建失败
集成问题

尤其在以下情况必须使用：

时间紧迫（紧急情况最容易让人猜测式修复）
觉得"一个小修改"就能搞定
已经尝试了多种修复
上一次修复没有生效
你没有完全理解问题

以下情况也不要跳过：

问题看起来很简单（简单的 bug 也有根本原因）
你很赶时间（越急越容易返工）
领导要求立刻修好（系统化调试比反复尝试更快）

四个阶段

你必须完成每个阶段后才能进入下一个。

第一阶段：根因调查

在尝试任何修复之前：

仔细阅读错误信息
- 不要跳过错误或警告
- 它们往往直接包含解决方案
- 完整阅读堆栈跟踪
- 记下行号、文件路径、错误码
稳定复现
- 你能可靠地触发它吗？
- 具体的复现步骤是什么？
- 每次都能复现吗？
- 如果无法复现 → 收集更多数据，不要猜测
检查近期变更
- 什么变更可能导致了这个问题？
- git diff、最近的提交
- 新依赖、配置变更
- 环境差异
在多组件系统中收集证据

当系统有多个组件时（CI → 构建 → 签名，API → 服务 → 数据库）：

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Systematic Debugging

What else does jnMetaCode publish alongside Systematic Debugging?
Systematic Debugging is one of 20 skills that DirSkills catalogs from jnMetaCode/superpowers-zh, the repository it ships in. Its siblings there include Brainstorming, Chinese Code Review and Chinese Commit Conventions. Each one is a separate skill with its own page in this directory, installs the same way Systematic Debugging does, and is maintained by jnMetaCode in that same repository. The rest of the collection is listed on the jnMetaCode/superpowers-zh page.
How does Systematic Debugging compare to other Quality skills?
Systematic Debugging ranks #237 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Systematic Debugging against them. Open each page to compare what they document and how they install.