{"id":30260745,"url":"https://github.com/redpop/claude-code-toolkit","last_synced_at":"2025-08-15T19:56:18.278Z","repository":{"id":306831985,"uuid":"1027300341","full_name":"redpop/claude-code-toolkit","owner":"redpop","description":"Comprehensive toolkit extending Claude Code with 70+ slash commands, specialized AI agents, and automation workflows. Features hybrid parallel-scanning architecture, intelligent problem routing, and automated code quality improvements. One-command pipelines for security audits, performance optimization, and refactoring.","archived":false,"fork":false,"pushed_at":"2025-08-13T09:18:10.000Z","size":729,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2025-08-13T09:26:07.678Z","etag":null,"topics":["ai-agents","ai-powered","automation","claude","claude-ai","code-analysis","code-quality","developer-tools","mcp","performance-optimization","security-analysis","slash-commands","workflow-automation"],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/redpop.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2025-07-27T18:25:18.000Z","updated_at":"2025-08-13T09:18:14.000Z","dependencies_parsed_at":"2025-08-13T19:30:27.520Z","dependency_job_id":null,"html_url":"https://github.com/redpop/claude-code-toolkit","commit_stats":null,"previous_names":["redpop/claude-code-toolkit"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/redpop/claude-code-toolkit","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/redpop%2Fclaude-code-toolkit","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/redpop%2Fclaude-code-toolkit/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/redpop%2Fclaude-code-toolkit/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/redpop%2Fclaude-code-toolkit/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/redpop","download_url":"https://codeload.github.com/redpop/claude-code-toolkit/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/redpop%2Fclaude-code-toolkit/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":270624264,"owners_count":24618262,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-15T02:00:12.559Z","response_time":110,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ai-agents","ai-powered","automation","claude","claude-ai","code-analysis","code-quality","developer-tools","mcp","performance-optimization","security-analysis","slash-commands","workflow-automation"],"created_at":"2025-08-15T19:56:14.754Z","updated_at":"2025-08-15T19:56:18.269Z","avatar_url":"https://github.com/redpop.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Claude Code Toolkit\n\nThe complete toolkit for extending Claude Code with commands, agents, and tools. A comprehensive collection of slash commands, AI agents, and utilities that can be installed in `~/.claude/` with a custom prefix.\n\n## 🚀 Quick Start: Transform Your Code Quality\n\n### Recommended 3-Step Workflow for Project Optimization\n\n```bash\n# Step 1: Deep analysis with automatic report generation\n/prefix:scan:deep . --export-json\n# Creates: analysis-YYYYMMDD-HHMMSS.json\n\n# Step 2: Generate action plan from latest report\n/prefix:scan:report --latest --generate-action-plan\n# Creates: action-plan-YYYYMMDD-HHMMSS.md\n\n# Step 3: Execute the improvements\n/prefix:auto:execute --latest\n```\n\n### Alternative Quick Workflows\n\n**2-Step Quick Check:**\n\n```bash\n/prefix:scan:quick . --export-json    # Fast scan\n/prefix:fix:quick-wins --latest       # Apply immediate fixes\n```\n\n**One-Command Pipeline:**\n\n```bash\n/prefix:meta:pipelines deep-quality    # Complete quality improvement\n```\n\n### 💡 Pro Tips\n\n- `--export-json` without filename → Auto-generates timestamped files\n- `--latest` → Automatically finds the most recent report\n- Commands can be chained: `/prefix:meta:chain \"scan:deep .\" -\u003e \"fix:quick-wins {output}\"`\n\n**[See Full Workflow Guide →](docs/guides/MODERN-WORKFLOW.md)**\n\n## Installation\n\n### Step 1: Clone the Repository\n\n```bash\n# Clone the official repository\ngit clone https://github.com/redpop/claude-code-toolkit.git\ncd claude-code-toolkit\n\n# Or clone your fork\ngit clone https://github.com/YourUsername/your-fork.git\ncd your-fork\n```\n\n### Step 2: Install with Your Prefix\n\n```bash\n# Install with your chosen prefix (e.g., \"myprefix\", \"global\", etc.)\n./install.sh myprefix\n```\n\nThe installation script will:\n\n- Copy command files to `~/.claude/commands/myprefix/`\n- Install AI agents to `~/.claude/agents/`\n- Display all available commands and agents after installation\n- Create backups of existing installations if needed\n\n## Forking This Repository\n\nForking this repository allows you to:\n\n- Create and maintain your own custom commands\n- Share team-specific tools and workflows\n- Contribute back improvements to the original repository\n- Customize command behaviors for your specific needs\n\n### Step-by-Step Forking Instructions\n\n1. **Fork on GitHub**\n\n   - Visit the [original repository](https://github.com/redpop/claude-code-toolkit)\n   - Click the \"Fork\" button in the top right\n   - Choose your account/organization as the destination\n\n2. **Clone and Install Your Fork**\n\n   ```bash\n   # Clone your fork\n   git clone https://github.com/YourUsername/your-fork.git\n   cd your-fork\n\n   # Install with your chosen prefix\n   ./install.sh myprefix\n   ```\n\n3. **Verify Installation**\n\n   ```bash\n   # Check that commands are installed\n   ls ~/.claude/commands/myprefix/\n\n   # Check that agents are installed\n   ls ~/.claude/agents/\n   ```\n\n### Benefits of Forking\n\n- **Custom Commands**: Add proprietary or project-specific commands without affecting the original repository\n- **Team Collaboration**: Share standardized workflows across your organization\n- **Experimentation**: Test new command ideas before contributing upstream\n- **Version Control**: Maintain your own release cycle and versioning\n\n## Custom Prefix Support\n\nYou can install multiple command sets with different prefixes:\n\n```bash\n# Install the original toolkit\ngit clone https://github.com/redpop/claude-code-toolkit.git toolkit-original\ncd toolkit-original\n./install.sh global\n\n# Install your team's fork\ncd ..\ngit clone https://github.com/YourTeam/team-commands.git toolkit-team\ncd toolkit-team\n./install.sh team\n```\n\nThis allows you to have both the original commands and your fork's commands available simultaneously:\n\n## Usage\n\nAfter installation, all commands are available with your chosen prefix:\n\n```\n# Original repository commands\n/global:git:commit\n/global:ai:handoff\n/global:project:changelog\n\n# Fork-specific commands\n/team:deploy:staging\n/team:testing:integration\n/team:internal:setup\n```\n\n## Updates\n\nTo update your installation:\n\n```bash\n# 1. Pull the latest changes in your cloned repository\ncd /path/to/claude-code-toolkit\ngit pull\n\n# 2. Re-run the installation\n./install.sh myprefix\n```\n\nThe installation script will:\n\n- Back up your existing installation (if you choose to)\n- Copy the latest versions of all commands and agents\n- Display the updated command list\n\n## Command Categories\n\nCommands are organized into logical categories for different workflows:\n\n### 🔍 **Scan** - Analysis \u0026 Investigation\n\nDeep code analysis, quality metrics, dependency tracing, and comprehensive scanning\n\n### 🔧 **Fix** - Direct Corrections\n\nAutomated fixes for security issues, performance problems, code duplication, and documentation\n\n### 🏭 **Gen** - Code \u0026 Documentation Generation\n\nGenerate tests, documentation, configurations, and other project artifacts\n\n### 🌊 **Flow** - Multi-Agent Workflows\n\nIntelligent problem routing, parallel analysis, and coordinated multi-agent operations\n\n### 🤖 **Auto** - Automation \u0026 Orchestration\n\nSprint planning, continuous monitoring, and automated execution of improvement plans\n\n### 🔒 **Sec** - Security Operations\n\nSecurity audits, compliance checking, and vulnerability management\n\n### 🗂️ **Git** - Version Control\n\nEnhanced git operations with intelligent commit messages and workflow integration\n\n### 🎯 **Meta** - Project \u0026 Toolkit Management\n\nProject health checks, command chaining, export management, and toolkit utilities\n\n## Available Commands\n\nAll commands require your chosen prefix (e.g., `myprefix`). Commands follow a consistent pattern: `/prefix:category:command`\n\n\u003c!-- COMMANDS:START - DO NOT EDIT --\u003e\n\n### Auto Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:auto:execute` | Execute action plans systematically with progress tracking and smart error handling | `\u003caction-plan.md\u003e\\|--latest`, `--mode=supervised\\|auto`, `--dry-run`, `--parallel=N` |\n| `/prefix:auto:monitor` | Set up and manage continuous code quality monitoring with automated analysis, fixes, and reporting | `directory`, `--schedule=daily\\|weekly\\|commit`, `--auto-fix=safe\\|all\\|none`, `--notify=email\\|slack\\|github` |\n| `/prefix:auto:report` | Generate comprehensive completion report after action plan execution, showing results, metrics, and next steps | `--action-plan=\u003cfile\u003e`, `--execution-log=\u003cfile\u003e`, `--compare-baseline`, `--export-formats=md,json,html` |\n| `/prefix:auto:sprint` | Plan and execute a complete code quality improvement sprint with analysis, prioritization, fixes, and tracking | `directory`, `--duration=1w\\|2w\\|1m`, `--team-size=N`, `--focus=security\\|performance\\|quality\\|all` |\n\n\n### Fix Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:fix:documentation` | Fix documentation issues including broken links, parameter mismatches, missing cross-references, and outdated content | `report.json\\|directory`, `--fix-links`, `--fix-params`, `--add-deprecation`, `--dry-run`, `--interactive` |\n| `/prefix:fix:duplicates` | Remove code duplication by extracting common functions, creating shared utilities, and applying DRY principles | `report.json\\|directory`, `--threshold=80`, `--min-lines=5`, `--dry-run`, `--create-utils` |\n| `/prefix:fix:performance` | Automated performance issue fixes including O(n²) algorithms, memory optimization, and database batching | `--target=algorithm\\|memory\\|database\\|all`, `--file=path`, `--dry-run` |\n| `/prefix:fix:quick-wins` | Apply high-ROI fixes from analysis reports - quick wins with maximum impact and minimal effort | `report.json`, `--dry-run`, `--category=security\\|performance\\|quality`, `--max-effort=4h`, `--min-roi=5` |\n| `/prefix:fix:security` | Fix security vulnerabilities with MCP-enhanced analysis or traditional pattern matching | `report.json`, `--severity=critical,high,medium`, `--dry-run`, `--interactive`, `--owasp-top10` |\n| `/prefix:fix:shell` | Automatically fix shell script issues using shellcheck analysis | `path/file`, `--check-only`, `--strict`, `--summary-only` |\n\n\n### Flow Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:flow:debug-mode` | Switch to intensive debugging mode for current problem | `--verbose`, `--trace` |\n| `/prefix:flow:incident` | Rapid incident response workflow for production issues with root cause analysis | `\u003cincident-description\u003e`, `--severity=critical\\|high\\|medium`, `--system=component` |\n| `/prefix:flow:refactor` | Intelligent refactoring suggestions with impact analysis and step-by-step guidance | `\u003cfile-or-pattern\u003e`, `--type=extract\\|rename\\|restructure`, `--safety=conservative\\|balanced\\|aggressive` |\n| `/prefix:flow:review` | Comprehensive code review using multiple specialized agents for different perspectives | `\u003cfile-or-directory\u003e`, `--focus=security\\|performance\\|architecture\\|all` |\n| `/prefix:flow:smart` | Intelligently analyze and route problems to the most appropriate specialized agents | `\u003cproblem-description\u003e`, `--verbose`, `--suggest-only` |\n\n\n### Gen Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:gen:docs` | Generate comprehensive documentation including API docs, README files, code comments, and architecture diagrams | `directory\\|file`, `--types=api,readme,comments,diagrams`, `--format=markdown,html`, `--update-existing` |\n| `/prefix:gen:format` | Create or convert content into various formats (HTML, Markdown, Confluence, Plain Text) | `\u003crequest-or-file\u003e`, `--html\\|--html-simple\\|--markdown\\|--confluence\\|--text` |\n| `/prefix:gen:tests` | Generate comprehensive test suites for uncovered code, including unit tests, integration tests, and edge cases | `report.json\\|file\\|directory`, `--coverage-target=80`, `--framework=auto`, `--types=unit,integration`, `--mock-externals` |\n\n\n### Git Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:git:commit` | Creates structured Git commits with Conventional Commit format and emojis | `--no-verify`, `--fast`, `--push` |\n\n\n### Meta Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:meta:analyze-toolkit` | Analyze toolkit commands and agents for redundancies, inconsistencies, and refactoring opportunities | `--fix`, `--export-json`, `--export-md`, `--focus=\u003carea\u003e` |\n| `/prefix:meta:chain` | Chain commands or execute pre-defined pipelines with intelligent data flow | `\u003cpipeline-name`, `\\|`, `command-chain\u003e`, `--list`, `--save-as=name`, `--dry-run` |\n| `/prefix:meta:changelog` | AI-powered CHANGELOG.md management that automatically determines version based on changes | `--analyze`, `--commit`, `--push`, `--update-version` |\n| `/prefix:meta:create` | Intelligently create commands, agents, or workflows from your description | `\u003cwhat`, `you`, `need\u003e`, `--type=auto\\|command\\|agent\\|workflow` |\n| `/prefix:meta:export` | Unified export management for all analysis results with format conversion | `\u003creport-files...\u003e`, `--format=md\\|json\\|html\\|pdf`, `--merge`, `--template=name` |\n| `/prefix:meta:find-cmd` | Find the best command for your task from all available commands (global and local) | `\u003ctask-description\u003e`, `--all`, `--local-only`, `--global-only` |\n| `/prefix:meta:handoff` | Documents current problem context for handoff to another AI assistant | `output-file` |\n| `/prefix:meta:health` | Comprehensive project health check with actionable insights and trend analysis | `--verbose`, `--compare=last-check.json`, `--export` |\n| `/prefix:meta:summary` | Creates a chat summary for another AI with complete context | `summaries/` |\n| `/prefix:meta:test-guide` | Generates interactive test guides for recent changes, suitable for both end-users and technical reviewers | `--type=all\\|user\\|technical`, `--format=md\\|checklist\\|jira`, `--lang=en\\|de\\|es\\|fr`, `--output=file.md` |\n| `/prefix:meta:update-docs` | Intelligently updates project documentation based on code changes and implementation status | `--scope=\u003ctype\u003e`, `--analyze`, `--commit` |\n| `/prefix:meta:version` | Check installed toolkit version and available updates | `check\\|update` |\n\n\n### Scan Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:scan:deep` | Deep code analysis with streamlined output and clear workflow guidance | `\u003cdirectory\u003e`, `--focus=security\\|performance\\|architecture\\|all`, `--export-md`, `--export-json` |\n| `/prefix:scan:deps` | In-depth dependency analysis with 6 specialized agents for complete transparency | `package-name\\|file`, `--depth=direct\\|transitive\\|full`, `--check=security\\|licenses\\|all` |\n| `/prefix:scan:docs` | Analyze documentation health, validate code-doc synchronization, check cross-references, and identify outdated content | `directory`, `--scope=readme\\|api\\|all`, `--check-links`, `--validate-params`, `--export-report` |\n| `/prefix:scan:explore` | Multi-Perspective Deep Research with 8 different viewpoints on a topic | `topic`, `--depth=surface\\|medium\\|deep`, `--focus=technical\\|business\\|all` |\n| `/prefix:scan:map` | Creates a comprehensive codebase mapping with 10 agents for different aspects | `directory`, `--format=markdown\\|json\\|mermaid`, `--depth=overview\\|detailed\\|full` |\n| `/prefix:scan:perf` | Deep Performance Profiling with 7 Agents for Bottleneck Identification and Optimization | `directory`, `--profile=cpu\\|memory\\|io\\|all`, `--export-md`, `--export-json`, `--export-html`, `--export-all`, `--export-dir=path` |\n| `/prefix:scan:quality` | Comprehensive code quality metrics with trend analysis and improvement roadmap | `\u003cdirectory\u003e`, `--baseline=previous.json`, `--threshold=80`, `--export` |\n| `/prefix:scan:quick` | Quick parallel code analysis for rapid feedback (30 seconds) | `\u003cdirectory\u003e`, `--focus=area`, `--export-json` |\n| `/prefix:scan:refactor` | Analyzes the impact of refactoring changes using 6 specialized agents | `file-or-pattern`, `--change-type=rename\\|move\\|signature\\|structure` |\n| `/prefix:scan:report` | Intelligent analysis of code quality reports with trend detection, prioritization, and actionable insights | `report.json`, `--latest`, `--compare=other-report.json`, `--history`, `--trends`, `--quick-wins`, `--export-md`, `--generate-action-plan` |\n| `/prefix:scan:root-cause` | Deep root cause analysis with ultra intensive reasoning | `issue_description` |\n| `/prefix:scan:tests` | Comprehensive test coverage analysis with 5 specialized agents for test quality | `directory`, `--framework=jest\\|pytest\\|go-test\\|cargo-test`, `--export-md`, `--export-json`, `--export-html`, `--export-all`, `--export-dir=path` |\n\n\n### Sec Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:sec:audit` | Comprehensive security audit with MCP-enhanced scanning or traditional fallback methods | `directory`, `--severity=critical\\|high\\|all`, `--export-md`, `--export-json`, `--export-html`, `--export-all`, `--export-dir=path` |\n| `/prefix:sec:baseline` | Establish and track security baseline with MCP-enhanced scanning or traditional methods | `directory`, `--export-baseline`, `--compare=previous-baseline.json`, `--track-improvements` |\n| `/prefix:sec:comply` | Run compliance checks for OWASP, PCI-DSS, GDPR, and custom security policies | `directory`, `--standard=owasp\\|pci-dss\\|gdpr\\|all`, `--custom-rules=rules.yaml`, `--export-report` |\n\n\n### Typo3 Commands\n\n| Command | Description | Options |\n|---------|-------------|---------|\n| `/prefix:typo3:content-blocks` | Generate TYPO3 Content Blocks v1.3 with modern field configurations | `name`, `--type=element\\|page`, `--fields=...`, `--sitepackage=path` |\n| `/prefix:typo3:extension-kickstarter` | Create TYPO3 extensions using ext-kickstarter or manual scaffolding | `extension-key`, `--type=...`, `--use-kickstarter`, `--composer-name=...` |\n| `/prefix:typo3:fluid-components` | Generate Fluid v4 Components for TYPO3 v13 with Atomic Design patterns | `component-name`, `--type=atom\\|molecule\\|organism`, `--sitepackage=path` |\n| `/prefix:typo3:make-content-block` | Wrapper for TYPO3 make:content-block command with intelligent defaults | `--vendor=...`, `--type=...`, `--skeleton-path=...`, `--config-path=...` |\n| `/prefix:typo3:sitepackage` | Create a TYPO3 v13.4 SitePackage based on official template with Site Sets | `vendor`, `package-name`, `--options` |\n\n\u003c!-- COMMANDS:END --\u003e\n\n## Sub-Agents\n\n### Introduction to Sub-Agents\n\nThe Sub-Agents feature introduces a powerful new paradigm for complex code analysis and operations. By leveraging Claude's Task Tool capability to spawn multiple specialized AI agents, these commands can perform parallel analysis, cross-reference findings, and deliver comprehensive insights that would be impossible with sequential processing.\n\nEach sub-agent operates independently with its own specialized focus area, then contributes its findings to a coordinated final report. This approach enables:\n\n- **10x faster analysis** through parallel processing\n- **Deeper insights** from specialized perspectives\n- **Cross-validation** of findings between agents\n- **Comprehensive coverage** of complex codebases\n\n### Available Specialized Sub-Agents\n\nOur sub-agent system includes seven core specialists that can be combined in various ways:\n\n#### 1. Security Specialist 🔒\n\n- **Expertise**: Vulnerability detection, authentication flows, encryption practices\n- **Focus Areas**: SQL injection, XSS, CSRF, authentication bypasses, cryptographic weaknesses\n- **Output**: Security risk matrix, vulnerability reports, remediation recommendations\n\n#### 2. Performance Optimizer ⚡\n\n- **Expertise**: Algorithm complexity, memory management, query optimization\n- **Focus Areas**: O(n) analysis, memory leaks, database bottlenecks, caching opportunities\n- **Output**: Performance hotspots, optimization strategies, benchmark comparisons\n\n#### 3. Test Engineer 🧪\n\n- **Expertise**: Test coverage analysis, edge case identification, test quality assessment\n- **Focus Areas**: Missing tests, flaky tests, test pyramid analysis, mock usage\n- **Output**: Coverage reports, test improvement plans, edge case scenarios\n\n#### 4. Code Architect 🏗️\n\n- **Expertise**: Design patterns, architectural principles, dependency management\n- **Focus Areas**: SOLID violations, coupling analysis, modularity assessment, API design\n- **Output**: Architecture diagrams, refactoring roadmaps, design pattern recommendations\n\n#### 5. Refactoring Expert 🔧\n\n- **Expertise**: Code smells, technical debt, maintainability improvements\n- **Focus Areas**: Duplicate code, complex methods, naming conventions, dead code\n- **Output**: Refactoring priorities, code quality metrics, improvement strategies\n\n#### 6. Documentation Health Specialist 📚\n\n- **Expertise**: Documentation quality, code-doc synchronization, technical writing best practices\n- **Focus Areas**: Parameter validation, cross-reference checking, deprecation tracking, coverage analysis\n- **Output**: Health scores, broken link reports, parameter mismatches, improvement recommendations\n\n#### 7. Report Analyzer 📊\n\n- **Expertise**: Code quality report analysis, trend detection, prioritization strategies\n- **Focus Areas**: ROI analysis, quick wins identification, historical comparisons, sprint planning\n- **Output**: Prioritized action items, trend reports, implementation roadmaps\n\n### Hybrid Commands: Task Tool + Sub-Agents\n\nThe true power of sub-agents emerges in hybrid commands that orchestrate multiple specialists for comprehensive analysis:\n\n#### Orchestration Commands\n\n- **`/prefix:orchestration:analyze-parallel`**: Deploys 10 parallel agents for ultra-fast code analysis\n- **`/prefix:orchestration:security-audit`**: 8 security-focused agents for comprehensive vulnerability scanning\n- **`/prefix:orchestration:performance-scan`**: 7 agents profiling different performance aspects\n- **`/prefix:orchestration:test-coverage`**: 5 agents analyzing test quality from multiple angles\n- **`/prefix:orchestration:refactor-impact`**: 6 agents assessing refactoring risks and benefits\n\n#### Research Commands\n\n- **`/prefix:research:deep-dive`**: 8 agents providing different perspectives on technical topics\n- **`/prefix:research:codebase-map`**: 10 agents creating comprehensive codebase documentation\n- **`/prefix:research:dependency-trace`**: 6 agents analyzing dependency chains and impacts\n\n### Example: Using the analyze-deep Hybrid Command\n\nThe `analyze-parallel` command demonstrates the power of orchestrated sub-agents:\n\n```bash\n# Analyze a complex module with 10 parallel agents\n/myprefix:orchestration:analyze-parallel src/core --focus=security\n\n# Output structure:\n📊 PARALLEL ANALYSIS REPORT\n========================\n\n🔒 Security Agent Findings:\n- Critical: Unvalidated user input in auth.js:142\n- High: Missing CSRF protection in api/endpoints.js\n- Medium: Weak password hashing algorithm\n\n⚡ Performance Agent Findings:\n- Bottleneck: O(n²) algorithm in data-processor.js\n- Memory leak: Unclosed database connections\n- Optimization: Cache opportunity for repeated API calls\n\n🏗️ Architecture Agent Findings:\n- SOLID Violation: Single Responsibility in UserService\n- High Coupling: Direct database access in controllers\n- Missing abstraction layer for external APIs\n\n[... 7 more agent reports ...]\n\n🎯 CONSOLIDATED RECOMMENDATIONS:\n1. Immediate: Fix security vulnerabilities (2 critical, 5 high)\n2. Short-term: Implement caching layer (30% performance gain)\n3. Long-term: Refactor to hexagonal architecture\n```\n\n### Benefits of Sub-Agent Architecture\n\n1. **Parallel Processing**: Multiple agents work simultaneously, reducing analysis time from hours to minutes\n2. **Specialized Expertise**: Each agent brings deep knowledge in its domain\n3. **Comprehensive Coverage**: No aspect is overlooked when multiple specialists collaborate\n4. **Cross-Validation**: Agents can verify and enhance each other's findings\n5. **Scalability**: Easy to add new specialist agents or create custom combinations\n\n### Creating Custom Sub-Agent Commands\n\nYou can create your own sub-agent orchestrations using the provided templates:\n\n```bash\n# Use the analysis template for code analysis scenarios\n/myprefix:project:create-command \"Create a sub-agent command that analyzes API endpoints for REST best practices\"\n\n# Use the research template for information gathering\n/myprefix:project:create-command \"Create a research command that investigates modern authentication methods\"\n```\n\nThe sub-agent system represents a paradigm shift in how AI assistants approach complex software engineering tasks, enabling unprecedented depth and speed of analysis.\n\n## Maintaining Your Fork\n\nKeeping your fork up-to-date and contributing back to the community ensures everyone benefits from improvements.\n\n### Syncing with Upstream\n\n1. **Add the upstream remote** (one-time setup)\n\n   ```bash\n   cd /path/to/your/fork\n   git remote add upstream https://github.com/redpop/claude-code-toolkit.git\n   git remote -v  # Verify remotes\n   ```\n\n2. **Fetch and merge upstream changes**\n\n   ```bash\n   # Fetch upstream changes\n   git fetch upstream\n\n   # Merge into your main branch\n   git checkout main\n   git merge upstream/main\n\n   # Push to your fork\n   git push origin main\n   ```\n\n3. **Update your installations**\n   ```bash\n   # Update each installation\n   cd ~/.claude/commands/myprefix\n   git pull\n   ```\n\n### Contributing Back to Upstream\n\nWhen you've created a useful command that could benefit the community:\n\n1. **Ensure your command is general-purpose**\n\n   - Remove any company-specific or proprietary logic\n   - Use clear, descriptive naming\n   - Include comprehensive documentation\n\n2. **Create a feature branch**\n\n   ```bash\n   git checkout -b feature/new-command\n   git add commands/category/new-command.md\n   git commit -m \"✨ feat: add new-command for X functionality\"\n   git push origin feature/new-command\n   ```\n\n3. **Submit a pull request**\n   - Visit your fork on GitHub\n   - Click \"Compare \u0026 pull request\"\n   - Describe your command and its use cases\n   - Reference any related issues\n\n### Best Practices for Fork Management\n\n1. **Organize Custom Commands**\n\n   ```\n   commands/\n   ├── team/           # Team-specific commands\n   ├── project/        # Project-specific commands\n   ├── internal/       # Internal tools\n   └── experimental/   # Commands under development\n   ```\n\n2. **Document Your Commands**\n\n   - Always include frontmatter with `description` and `argument-hint`\n   - Add usage examples in the command file\n   - Update your fork's README with team-specific instructions\n\n3. **Version Control Strategy**\n\n   - Tag releases for your team (`v1.0.0-team`)\n   - Maintain a CHANGELOG for your custom commands\n   - Use semantic versioning for breaking changes\n\n4. **Testing Commands**\n\n   ```bash\n   # Test in isolation\n   ~/.claude/commands/test-prefix/\n\n   # Validate command structure\n   ./scripts/update-readme.sh\n   ```\n\n5. **Security Considerations**\n   - Never commit sensitive data or credentials\n   - Use environment variables for configuration\n   - Review commands before sharing with your team\n\n## Adding Custom Commands\n\n1. Create a new folder under `commands/` for your category\n2. Create a `.md` file with your command name\n3. Write your command logic as a Markdown prompt\n\n### Example structure for a new command:\n\n```\n# In original repository or fork\ncommands/\n└── my-category/\n    └── my-command.md\n\n# Fork-specific organization\ncommands/\n├── team/              # Team-specific commands\n│   └── deploy.md     # Available as: /team:team:deploy\n├── project/           # Project tools\n│   └── setup.md      # Available as: /team:project:setup\n└── my-category/       # General commands\n    └── my-command.md  # Available as: /team:my-category:my-command\n```\n\n## Command Naming Conventions\n\n- Use descriptive names in lowercase\n- Separate words with hyphens (`-`)\n- Group related commands in common folders\n\n## Maintaining Commands\n\nWhen adding or modifying commands:\n\n1. Ensure each command has proper frontmatter with `description` and optional `argument-hint`\n2. Run `./scripts/update-readme.sh` to update the command list below\n3. The \"Available Commands\" section is auto-generated - do not edit manually\n\n## Key Features\n\n### 🚀 Intelligent Multi-Agent System\n\n- **Parallel Processing**: Run up to 10 specialized agents simultaneously\n- **Smart Routing**: AI automatically determines which agents to use\n- **Cross-Validation**: Agents validate each other's findings\n- **Deep Expertise**: Each agent has specialized domain knowledge\n\n### 🔄 Advanced Command Chaining\n\n- **Data Flow**: Automatic output passing between commands\n- **Error Handling**: Intelligent error recovery and fallbacks\n- **Conditional Logic**: Execute commands based on results\n- **Pipeline Templates**: Pre-built workflows for common tasks\n\n### 📊 Comprehensive Analysis\n\n- **Multi-Dimensional**: Security, performance, architecture, and quality\n- **Trend Detection**: Track improvements over time\n- **ROI Prioritization**: Focus on high-impact changes\n- **Export Flexibility**: Multiple formats (MD, JSON, HTML, PDF)\n\n### 🤖 Automation First\n\n- **Action Plans**: Executable improvement plans\n- **Progress Tracking**: Real-time status updates\n- **Batch Operations**: Fix multiple issues automatically\n- **Quality Gates**: Enforce standards in CI/CD\n\n## Contributing\n\n1. Fork the repository\n2. Create a feature branch\n3. Add your commands with proper frontmatter\n4. Run `./scripts/update-readme.sh` to update documentation\n5. Create a pull request\n\nSee [CLAUDE.md](CLAUDE.md) for development guidelines.\n\n## License\n\nMIT License - see [LICENSE](LICENSE) file for details.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fredpop%2Fclaude-code-toolkit","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fredpop%2Fclaude-code-toolkit","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fredpop%2Fclaude-code-toolkit/lists"}