메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Calibrate the Claude Code statusline against the real /usage numbers. Use when the user shares a screenshot of the in-app `/usage` panel (or the claude.ai Settings → Usage page) and wants the statusline's "time left", session %, and weekly % to match what Claude actually reports. Fixes ccusage block-drift, where the local 5-hour clock starts from the first transcript message instead of the real server-side reset.
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.
Use when the user wants a second opinion from Gemini or OpenAI/ChatGPT, asks to "consult" another model, or wants to compare responses across models. This is the interactive MCP chat path for a second opinion or model comparison; to run a structured review gate over code, diffs, plans, or large doc corpora through a headless CLI, use cli-review instead.
Use this skill when deciding whether and how to update the knowledge base at /path/to/works/for/you/knowledge_base/ after completing a task. This is the post-task "does this work belong in the KB, and where" decision path; to turn a pasted LLM conversation transcript into a KB note use kb-from-conversation instead.
Periodic review of the memory system at ~/.claude/memory/ for duplicates, redundancies, conflicts, and stale entries. Use when the user asks to audit, clean up, or review memory. Presents findings with enforcement trade-off context — never retires anything without user confirmation. Scoped to the agent memory files under ~/.claude/memory/; for the same kind of duplicate/stale/conflict audit over the knowledge base at /path/to/works/for/you/knowledge_base/ use kb-sweep instead.
Use this skill when the user wants to "promote", "move", "upgrade", or "migrate" a project-level skill, agent, or rule (e.g. a Cursor rule, a project-local AI rule, or any .md skill/agent file) into a global Claude scope. By default always promotes to global (~/.claude/skills/, ~/.claude/agents/, ~/.claude/CLAUDE.md) unless the user explicitly says "project-level". Moves the file so it is shared across all projects and symlinks it back so the original project is not broken. This keeps the skill private to your global ~/.claude scope; to publish skills to the public agent_skills GitHub repo, use publish-skills instead.
| 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")