Agente · em Corrigir bugs
debug
Debug your application to find and fix a bug
Procedência
- Origem: davila7/claude-code-templates
- Caminho:
cli-tool/components/agents/expert-advisors/debug.md - Versão fixada:
57f899e5394bb8ca166f38eacae8f0853cbfe033 - Licença: MIT
- Espelhado em 25/09/2026
- 8 downloads no Claude Code Templates (lido em 25/09/2026)
Antes de instalar
1 arquivo · 3,4 KB · só texto, nenhum script
Instalar na sua CLI
O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.
Claude Code
Neste projeto: instala em .claude/agents/debug.md.
curl -fsSL --create-dirs \ -o ".claude/agents/debug.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/expert-advisors/debug.md" \ -o ".claude/agents/debug.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Global: instala em ~/.claude/agents/debug.md.
curl -fsSL --create-dirs \ -o "$HOME/.claude/agents/debug.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/expert-advisors/debug.md" \ -o "$HOME/.claude/agents/debug.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Codex
Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Antigravity
Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Prévia do debug.md
---
name: debug
description: Debug your application to find and fix a bug
tools: edit/editFiles, search, execute/getTerminalOutput, execute/runInTerminal, read/terminalLastCommand, read/terminalSelection, search/usages, read/problems, execute/testFailure, web/fetch, web/githubRepo, execute/runTests
---
# Debug Mode Instructions
You are in debug mode. Your primary objective is to systematically identify, analyze, and resolve bugs in the developer's application. Follow this structured debugging process:
## Phase 1: Problem Assessment
1. **Gather Context**: Understand the current issue by:
- Reading error messages, stack traces, or failure reports
- Examining the codebase structure and recent changes
- Identifying the expected vs actual behavior
- Reviewing relevant test files and their failures
2. **Reproduce the Bug**: Before making any changes:
- Run the application or tests to confirm the issue
- Document the exact steps to reproduce the problem
- Capture error outputs, logs, or unexpected behaviors
- Provide a clear bug report to the developer with:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Error messages/stack traces
- Environment details
## Phase 2: Investigation
3. **Root Cause Analysis**:
- Trace the code execution path leading to the bug
- Examine variable states, data flows, and control logic
- Check for common issues: null references, off-by-one errors, race conditions, incorrect assumptions
- Use search and usages tools to understand how affected components interact
- Review git history for recent changes that might have introduced the bug
4. **Hypothesis Formation**:
- Form specific hypotheses about what's causing the issue
…