debug

分类: 工具与效率 | 上传者: serpentine-parser | 下载: 0 | 版本: v1.0（最新）

Diagnose and fix a bug or unexpected behavior.通过依赖关系图跟踪问题，根据需要添加日志记录，并提出修复方案。当某些东西损坏、产生错误输出或行为异常时使用。

更新日志: Source: GitHub https://github.com/serpentine-parser/serpentine

目录结构

当前层级: tree/main/.claude/skills/debug/

📄 SKILL.md 1.7 KB

SKILL.md

---
name: debug
description: Diagnose and fix a bug or unexpected behavior. Traces the problem through the dependency graph, adds logging if needed, and proposes a fix. Use when something is broken, producing wrong output, or behaving unexpectedly.
argument-hint: <description of the bug or unexpected behavior>
allowed-tools: Bash Read Edit Skill
---

Diagnose and fix: $ARGUMENTS

**Step 1 — Understand the problem**

Ask me what the intended behavior is, what the current output is, and how to reproduce it. Do not start investigating until you understand what "fixed" looks like.

**Step 2 — Trace through the graph**

Run `/serpentine-check <suspected function or module>` on the area where the bug likely lives. Use the edges to trace the call chain — follow `from`/`to` relationships to find where the bad data or wrong behavior originates.

If the bug could be in multiple places, run check on each candidate. If you don't know where to start, run `/serpentine-orient` first to find the relevant module boundaries.

Only read files that the analysis identifies as part of the call chain.

**Step 3 — Narrow down**

Don't overthink. If the graph narrows it to a few files but you're unsure which is the source, add logging statements to gain a better understanding. Run the code and read the output.

**Step 4 — Diagnose**

Write a brief diagnosis: what's broken, why, and which callsites are affected (from the serpentine check). Share it with me before proposing a fix.

**Step 5 — Wait for approval**

Propose the fix. Do not write any code until I approve. If the fix touches a function with a BREAKING verdict from check, list all affected callsites in the proposal.

登录后下载/点赞/收藏 ❤ 10 | ★ 0

debug

目录结构

SKILL.md

举报内容

提示