48 lines
1.6 KiB
Markdown
48 lines
1.6 KiB
Markdown
---
|
|
allowed-tools: [Read, Grep, Glob, Bash, TodoWrite, Task, WebSearch, WebFetch]
|
|
description: "Diagnose and resolve issues in code, builds, or system behavior"
|
|
wave-enabled: true
|
|
complexity-threshold: 0.7
|
|
---
|
|
|
|
# /hc:troubleshoot - Issue Diagnosis and Resolution
|
|
|
|
## Purpose
|
|
|
|
Systematically diagnose and resolve issues in code, builds, deployments, or system behavior.
|
|
|
|
## Usage
|
|
|
|
```bash
|
|
/hc:troubleshoot [issue] [--type bug|build|performance|deployment] [--trace]
|
|
```
|
|
|
|
## Arguments
|
|
|
|
- `issue` - Description of the problem or error message
|
|
- `--type` - Issue category (bug, build, performance, deployment)
|
|
- `--trace` - Enable detailed tracing and logging
|
|
- `--fix` - Automatically apply fixes when safe
|
|
|
|
## Execution
|
|
|
|
1. Use @agent-architect to analyze issue and gather initial context
|
|
2. For security issues, engage @agent-security-analyst
|
|
3. Identify potential root causes and investigation paths
|
|
4. Execute systematic debugging and diagnosis
|
|
5. Pass findings to @agent-coder for fix implementation
|
|
6. Use @agent-test-engineer to validate the fix
|
|
7. Apply fixes and verify resolution
|
|
|
|
**Wave Trigger**: Complex issues spanning >15 files or >3 domains
|
|
**Search Priority**: WebSearch > WebFetch for error resolution patterns
|
|
|
|
## Claude Code Integration
|
|
|
|
- Uses Task tool to orchestrate @agent-architect → @agent-coder → @agent-test-engineer workflow
|
|
- Uses Read for error log analysis
|
|
- Leverages Bash for runtime diagnostics
|
|
- Applies Grep for pattern-based issue detection
|
|
- Maintains structured troubleshooting documentation
|
|
- Shares diagnostic findings between agents via MCP memory server
|