mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
ab8904bc8c
Restored 26 additional commands from commitd4a17fc, bringing total from 5 to 30 commands. ## New Commands Added (26): - /analyze - Code and architecture analysis - /brainstorm - Structured brainstorming sessions - /build - Build and compilation workflows - /business-panel - Multi-expert business analysis - /cleanup - Code cleanup and refactoring - /design - System design and architecture - /document - Documentation generation - /estimate - Effort and time estimation - /explain - Code explanation - /git - Git operations and workflows - /help - Command help and usage - /implement - Implementation workflows - /improve - Code improvement suggestions - /index - Project indexing (alias for index-repo) - /load - Load saved sessions - /pm - Project management workflows - /reflect - Reflection and retrospectives - /save - Save current session - /select-tool - Tool selection guidance - /spawn - Spawn parallel tasks - /spec-panel - Multi-expert specification analysis - /task - Task management - /test - Testing workflows - /troubleshoot - Debugging and troubleshooting - /workflow - Custom workflow automation ## Documentation Updates: - Created docs/reference/commands-list.md with categorized command reference - Updated README.md with expandable 30-command list - Updated README-zh.md with Chinese translations - Updated README-ja.md with Japanese translations - Updated README-kr.md with Korean translations - Changed statistics: "3 plugins" → "30 commands" - Added command categories: Planning & Design, Development, Testing & Quality, Documentation, Version Control, Project Management, Research & Analysis, Utilities ## Files Changed: - 60 files changed, 7930 insertions(+), 267 deletions(-) - Added 26 commands to plugins/superclaude/commands/ - Added 26 commands to src/superclaude/commands/ - Created comprehensive command documentation Commands restored from:d4a17fc(superclaude/commands/) Total: 30 commands now available 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
88 lines
3.3 KiB
Markdown
88 lines
3.3 KiB
Markdown
---
|
|
name: troubleshoot
|
|
description: "Diagnose and resolve issues in code, builds, deployments, and system behavior"
|
|
category: utility
|
|
complexity: basic
|
|
mcp-servers: []
|
|
personas: []
|
|
---
|
|
|
|
# /sc:troubleshoot - Issue Diagnosis and Resolution
|
|
|
|
## Triggers
|
|
- Code defects and runtime error investigation requests
|
|
- Build failure analysis and resolution needs
|
|
- Performance issue diagnosis and optimization requirements
|
|
- Deployment problem analysis and system behavior debugging
|
|
|
|
## Usage
|
|
```
|
|
/sc:troubleshoot [issue] [--type bug|build|performance|deployment] [--trace] [--fix]
|
|
```
|
|
|
|
## Behavioral Flow
|
|
1. **Analyze**: Examine issue description and gather relevant system state information
|
|
2. **Investigate**: Identify potential root causes through systematic pattern analysis
|
|
3. **Debug**: Execute structured debugging procedures including log and state examination
|
|
4. **Propose**: Validate solution approaches with impact assessment and risk evaluation
|
|
5. **Resolve**: Apply appropriate fixes and verify resolution effectiveness
|
|
|
|
Key behaviors:
|
|
- Systematic root cause analysis with hypothesis testing and evidence collection
|
|
- Multi-domain troubleshooting (code, build, performance, deployment)
|
|
- Structured debugging methodologies with comprehensive problem analysis
|
|
- Safe fix application with verification and documentation
|
|
|
|
## Tool Coordination
|
|
- **Read**: Log analysis and system state examination
|
|
- **Bash**: Diagnostic command execution and system investigation
|
|
- **Grep**: Error pattern detection and log analysis
|
|
- **Write**: Diagnostic reports and resolution documentation
|
|
|
|
## Key Patterns
|
|
- **Bug Investigation**: Error analysis → stack trace examination → code inspection → fix validation
|
|
- **Build Troubleshooting**: Build log analysis → dependency checking → configuration validation
|
|
- **Performance Diagnosis**: Metrics analysis → bottleneck identification → optimization recommendations
|
|
- **Deployment Issues**: Environment analysis → configuration verification → service validation
|
|
|
|
## Examples
|
|
|
|
### Code Bug Investigation
|
|
```
|
|
/sc:troubleshoot "Null pointer exception in user service" --type bug --trace
|
|
# Systematic analysis of error context and stack traces
|
|
# Identifies root cause and provides targeted fix recommendations
|
|
```
|
|
|
|
### Build Failure Analysis
|
|
```
|
|
/sc:troubleshoot "TypeScript compilation errors" --type build --fix
|
|
# Analyzes build logs and TypeScript configuration
|
|
# Automatically applies safe fixes for common compilation issues
|
|
```
|
|
|
|
### Performance Issue Diagnosis
|
|
```
|
|
/sc:troubleshoot "API response times degraded" --type performance
|
|
# Performance metrics analysis and bottleneck identification
|
|
# Provides optimization recommendations and monitoring guidance
|
|
```
|
|
|
|
### Deployment Problem Resolution
|
|
```
|
|
/sc:troubleshoot "Service not starting in production" --type deployment --trace
|
|
# Environment and configuration analysis
|
|
# Systematic verification of deployment requirements and dependencies
|
|
```
|
|
|
|
## Boundaries
|
|
|
|
**Will:**
|
|
- Execute systematic issue diagnosis using structured debugging methodologies
|
|
- Provide validated solution approaches with comprehensive problem analysis
|
|
- Apply safe fixes with verification and detailed resolution documentation
|
|
|
|
**Will Not:**
|
|
- Apply risky fixes without proper analysis and user confirmation
|
|
- Modify production systems without explicit permission and safety validation
|
|
- Make architectural changes without understanding full system impact |