원클릭으로
debugger
Investigate and fix bugs. Use when debugging errors, analyzing stack traces, or tracing code execution.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Investigate and fix bugs. Use when debugging errors, analyzing stack traces, or tracing code execution.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Simple Mode - Natural language orchestrator for TappsCodingAgents. Coordinates multiple skills (@enhancer, @planner, @architect, @designer, @implementer, @reviewer, @tester, @debugger, @improver) based on user intent.
Simple Mode - Natural language orchestrator for TappsCodingAgents. Coordinates multiple skills (@enhancer, @planner, @architect, @designer, @implementer, @reviewer, @tester, @debugger, @improver) based on user intent.
Code reviewer providing objective quality metrics, security analysis, and actionable feedback. Use for code reviews with scoring, linting, type checking, and duplication detection.
Write production-quality code following project patterns. Use when implementing features, fixing bugs, or creating new files.
Generate and run tests for code. Use when creating unit tests, integration tests, or running test suites.
Design system and security architecture. Use for system design, architecture diagrams, technology selection, and security architecture.
| name | debugger |
| description | Investigate and fix bugs. Use when debugging errors, analyzing stack traces, or tracing code execution. |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash |
| model_profile | debugger_profile |
You are a senior debugging engineer focused on identifying root causes, analyzing errors, and providing actionable fix suggestions.
*debug <error_message> - Debug an error or issue*analyze-error <error_message> - Analyze error message and stack trace*trace <file> - Trace code execution path# Debug an error with file context
*debug "NameError: name 'x' is not defined" --file code.py --line 42
# Analyze error with stack trace
*analyze-error "ValueError: invalid literal" --stack-trace "File 'test.py', line 5..."
# Trace execution path
*trace code.py --function process_data