菜单
Use when the user reports a bug, asks to debug specific behavior, or when an unexpected failure occurs during execution. Applies the standing debugging protocol — reproduce, minimize, validate fix on a single job before scaling.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/allyoushawn/agent_skills --skill debug命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Generic skill for tasks that require planning, debugging, or iteration before they can be completed. Three modes — execute / optimization / orchestrate — selected by the request shape. Discriminator: does the task require planning? If the request is unambiguous and mechanical ("run this notebook with python3"), do NOT use this skill — direct execution is correct. If achieving the goal requires planning, recovery from failures, or iterating toward a target, this skill applies. Triggers: "use achieve-goal to X", "iterate to achieve metric Y", "execute this multi-milestone plan", or any goal that needs planning + recovery.
Dispatch a review task to Gemini CLI (large-context review — plans, docs, large file corpora) or Codex CLI (code review — diffs, PRs, implementation quality). Routes based on the nature of the artifact being reviewed. Use from achieve-goal, literature-survey skills, or any skill that needs a CLI-based review gate. This is a headless CLI review gate over a concrete artifact (code, diff, or doc corpus); for an interactive second opinion or a side-by-side model comparison via MCP chat, use consult-llm instead.
Composes a narrative "war story" history of how a line of work, a project, or a research direction evolved — what was tried, what was believed, what broke that belief, what changed, and where it's heading. Produces a mental-model document a newcomer (or future-self) can absorb. Use when the user asks for "the history of how X evolved", "a war story", "how did we get here", "the backstory/trajectory of this work", or wants the reasoning arc behind a series of decisions. Verifies factual and chronological claims against sources (NotebookLM if available) to avoid timing/inspiration contradictions, and ends with a CLI review gate.
基于 SOC 职业分类
正在显示 SKILL.md
| name | debug |
| description | Use when the user reports a bug, asks to debug specific behavior, or when an unexpected failure occurs during execution. Applies the standing debugging protocol — reproduce, minimize, validate fix on a single job before scaling. |
Apply the standing debugging protocol when investigating reported bugs or unexpected failures.
kb/context/debugging-protocol.md — the canonical protocol (reproduce → minimize → validate single → scale; log format; anti-patterns)~/.claude/skills/systematic-debugging/SKILL.md (obra/superpowers) — 4-phase root-cause structure used within this protocol; consult for the formal Hypothesize → Test → Observe → Refine cycle and root-cause-tracing.md~/.claude/skills/verification-before-completion/SKILL.md (obra/superpowers) — evidence gating before declaring a fix completekb/context/debugging-protocol.md if not already in contextgeneral-purpose subagent with a self-contained brief (per CLAUDE.md "Delegate Non-Trivial Editing")