claude-code-orchestrator-kit 1.4.0 → 1.4.15

package/.claude/skills/cleanup-health-inline/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: cleanup-health-inline
+description: Inline orchestration workflow for dead code detection and removal. Provides step-by-step phases for dead-code-hunter detection, priority-based cleanup with dead-code-remover, and verification cycles.
+version: 2.0.0
+---
+
+# Cleanup Health Check (Inline Orchestration)
+
+You ARE the orchestrator. Execute this workflow directly without spawning a separate orchestrator agent.
+
+## Workflow Overview
+
+```
+Detection → Validate → Remove by Priority → Verify → Repeat if needed
+```
+
+**Max iterations**: 3
+**Priorities**: critical → high → medium → low
+
+---
+
+## Phase 1: Pre-flight
+
+1. **Setup directories**:
+   ```bash
+   mkdir -p .tmp/current/{plans,changes,backups}
+   ```
+
+2. **Validate environment**:
+   - Check `package.json` exists
+   - Check `type-check` and `build` scripts exist
+
+3. **Initialize TodoWrite**:
+   ```json
+   [
+     {"content": "Dead code detection", "status": "in_progress", "activeForm": "Detecting dead code"},
+     {"content": "Remove critical dead code", "status": "pending", "activeForm": "Removing critical dead code"},
+     {"content": "Remove high priority dead code", "status": "pending", "activeForm": "Removing high dead code"},
+     {"content": "Remove medium priority dead code", "status": "pending", "activeForm": "Removing medium dead code"},
+     {"content": "Remove low priority dead code", "status": "pending", "activeForm": "Removing low dead code"},
+     {"content": "Verification scan", "status": "pending", "activeForm": "Verifying cleanup"}
+   ]
+   ```
+
+---
+
+## Phase 2: Detection
+
+**Invoke dead-code-hunter** via Task tool:
+
+```
+subagent_type: "dead-code-hunter"
+description: "Detect all dead code"
+prompt: |
+  Scan the entire codebase for dead code:
+  - Unused imports and exports
+  - Commented out code blocks
+  - Unreachable code
+  - Debug statements (console.log, debugger)
+  - Unused variables and functions
+  - Unused dependencies
+  - Categorize by priority (critical/high/medium/low)
+
+  Generate: dead-code-report.md
+
+  Return summary with dead code counts per priority.
+```
+
+**After dead-code-hunter returns**:
+1. Read `dead-code-report.md`
+2. Parse dead code counts by priority
+3. If zero dead code → skip to Final Summary
+4. Update TodoWrite: mark detection complete
+
+---
+
+## Phase 3: Quality Gate (Detection)
+
+Run inline validation:
+
+```bash
+pnpm type-check
+pnpm build
+```
+
+- If both pass → proceed to removal
+- If fail → report to user, exit
+
+---
+
+## Phase 4: Removal Loop
+
+**For each priority** (critical → high → medium → low):
+
+1. **Check if dead code exists** for this priority
+   - If zero → skip to next priority
+
+2. **Update TodoWrite**: mark current priority in_progress
+
+3. **Invoke dead-code-remover** via Task tool:
+   ```
+   subagent_type: "dead-code-remover"
+   description: "Remove {priority} dead code"
+   prompt: |
+     Read dead-code-report.md and remove all {priority} priority dead code.
+
+     For each item:
+     1. Backup file before editing
+     2. Remove dead code
+     3. Log change to .tmp/current/changes/cleanup-changes.json
+
+     Generate/update: dead-code-cleanup-summary.md
+
+     Return: count of removed items, count of failed removals.
+   ```
+
+4. **Quality Gate** (inline):
+   ```bash
+   pnpm type-check
+   pnpm build
+   ```
+
+   - If FAIL → report error, suggest rollback, exit
+   - If PASS → continue
+
+5. **Update TodoWrite**: mark priority complete
+
+6. **Repeat** for next priority
+
+---
+
+## Phase 5: Verification
+
+After all priorities cleaned:
+
+1. **Update TodoWrite**: mark verification in_progress
+
+2. **Invoke dead-code-hunter** (verification mode):
+   ```
+   subagent_type: "dead-code-hunter"
+   description: "Verification scan"
+   prompt: |
+     Re-scan codebase after cleanup.
+     Compare with previous dead-code-report.md.
+
+     Report:
+     - Dead code removed (count)
+     - Dead code remaining (count)
+     - New dead code introduced (count)
+   ```
+
+3. **Decision**:
+   - If dead_code_remaining == 0 → Final Summary
+   - If iteration < 3 AND dead_code_remaining > 0 → Go to Phase 2
+   - If iteration >= 3 → Final Summary with remaining items
+
+---
+
+## Phase 6: Final Summary
+
+Generate summary for user:
+
+```markdown
+## Cleanup Health Check Complete
+
+**Iterations**: {count}/3
+**Status**: {SUCCESS/PARTIAL}
+
+### Results
+- Found: {total} dead code items
+- Removed: {removed} ({percentage}%)
+- Remaining: {remaining}
+
+### By Priority
+- Critical: {removed}/{total}
+- High: {removed}/{total}
+- Medium: {removed}/{total}
+- Low: {removed}/{total}
+
+### Validation
+- Type Check: {status}
+- Build: {status}
+
+### Artifacts
+- Detection: `dead-code-report.md`
+- Cleanup: `dead-code-cleanup-summary.md`
+```
+
+---
+
+## Error Handling
+
+**If quality gate fails**:
+```
+Rollback available: .tmp/current/changes/cleanup-changes.json
+
+To rollback:
+1. Read changes log
+2. Restore files from .tmp/current/backups/
+3. Re-run workflow
+```
+
+**If worker fails**:
+- Report error to user
+- Suggest manual intervention
+- Exit workflow
+
+---
+
+## Key Differences from Old Approach
+
+| Old (Orchestrator Agent) | New (Inline Skill) |
+|--------------------------|-------------------|
+| 9+ orchestrator calls | 0 orchestrator calls |
+| ~1400 lines (cmd + agent) | ~150 lines |
+| Context reload each call | Single session context |
+| Plan files for each phase | Direct execution |
+| ~10,000+ tokens overhead | ~500 tokens |
+
+---
+
+## Worker Prompts
+
+See `references/worker-prompts.md` for detailed prompts.

package/.claude/skills/code-reviewer/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: code-reviewer
+description: Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when reviewing pull requests, providing code feedback, identifying issues, or ensuring code quality standards.
+---
+
+# Code Reviewer
+
+Complete toolkit for code reviewer with modern tools and best practices.
+
+## Quick Start
+
+### Main Capabilities
+
+This skill provides three core capabilities through automated scripts:
+
+```bash
+# Script 1: Pr Analyzer
+python scripts/pr_analyzer.py [options]
+
+# Script 2: Code Quality Checker
+python scripts/code_quality_checker.py [options]
+
+# Script 3: Review Report Generator
+python scripts/review_report_generator.py [options]
+```
+
+## Core Capabilities
+
+### 1. Pr Analyzer
+
+Automated tool for pr analyzer tasks.
+
+**Features:**
+- Automated scaffolding
+- Best practices built-in
+- Configurable templates
+- Quality checks
+
+**Usage:**
+```bash
+python scripts/pr_analyzer.py <project-path> [options]
+```
+
+### 2. Code Quality Checker
+
+Comprehensive analysis and optimization tool.
+
+**Features:**
+- Deep analysis
+- Performance metrics
+- Recommendations
+- Automated fixes
+
+**Usage:**
+```bash
+python scripts/code_quality_checker.py <target-path> [--verbose]
+```
+
+### 3. Review Report Generator
+
+Advanced tooling for specialized tasks.
+
+**Features:**
+- Expert-level automation
+- Custom configurations
+- Integration ready
+- Production-grade output
+
+**Usage:**
+```bash
+python scripts/review_report_generator.py [arguments] [options]
+```
+
+## Reference Documentation
+
+### Code Review Checklist
+
+Comprehensive guide available in `references/code_review_checklist.md`:
+
+- Detailed patterns and practices
+- Code examples
+- Best practices
+- Anti-patterns to avoid
+- Real-world scenarios
+
+### Coding Standards
+
+Complete workflow documentation in `references/coding_standards.md`:
+
+- Step-by-step processes
+- Optimization strategies
+- Tool integrations
+- Performance tuning
+- Troubleshooting guide
+
+### Common Antipatterns
+
+Technical reference guide in `references/common_antipatterns.md`:
+
+- Technology stack details
+- Configuration examples
+- Integration patterns
+- Security considerations
+- Scalability guidelines
+
+## Tech Stack
+
+**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin
+**Frontend:** React, Next.js, React Native, Flutter
+**Backend:** Node.js, Express, GraphQL, REST APIs
+**Database:** PostgreSQL, Prisma, NeonDB, Supabase
+**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI
+**Cloud:** AWS, GCP, Azure
+
+## Development Workflow
+
+### 1. Setup and Configuration
+
+```bash
+# Install dependencies
+npm install
+# or
+pip install -r requirements.txt
+
+# Configure environment
+cp .env.example .env
+```
+
+### 2. Run Quality Checks
+
+```bash
+# Use the analyzer script
+python scripts/code_quality_checker.py .
+
+# Review recommendations
+# Apply fixes
+```
+
+### 3. Implement Best Practices
+
+Follow the patterns and practices documented in:
+- `references/code_review_checklist.md`
+- `references/coding_standards.md`
+- `references/common_antipatterns.md`
+
+## Best Practices Summary
+
+### Code Quality
+- Follow established patterns
+- Write comprehensive tests
+- Document decisions
+- Review regularly
+
+### Performance
+- Measure before optimizing
+- Use appropriate caching
+- Optimize critical paths
+- Monitor in production
+
+### Security
+- Validate all inputs
+- Use parameterized queries
+- Implement proper authentication
+- Keep dependencies updated
+
+### Maintainability
+- Write clear code
+- Use consistent naming
+- Add helpful comments
+- Keep it simple
+
+## Common Commands
+
+```bash
+# Development
+npm run dev
+npm run build
+npm run test
+npm run lint
+
+# Analysis
+python scripts/code_quality_checker.py .
+python scripts/review_report_generator.py --analyze
+
+# Deployment
+docker build -t app:latest .
+docker-compose up -d
+kubectl apply -f k8s/
+```
+
+## Troubleshooting
+
+### Common Issues
+
+Check the comprehensive troubleshooting section in `references/common_antipatterns.md`.
+
+### Getting Help
+
+- Review reference documentation
+- Check script output messages
+- Consult tech stack documentation
+- Review error logs
+
+## Resources
+
+- Pattern Reference: `references/code_review_checklist.md`
+- Workflow Guide: `references/coding_standards.md`
+- Technical Guide: `references/common_antipatterns.md`
+- Tool Scripts: `scripts/` directory

package/.claude/skills/code-reviewer/references/code_review_checklist.md

@@ -0,0 +1,103 @@
+# Code Review Checklist
+
+## Overview
+
+This reference guide provides comprehensive information for code reviewer.
+
+## Patterns and Practices
+
+### Pattern 1: Best Practice Implementation
+
+**Description:**
+Detailed explanation of the pattern.
+
+**When to Use:**
+- Scenario 1
+- Scenario 2
+- Scenario 3
+
+**Implementation:**
+```typescript
+// Example code implementation
+export class Example {
+  // Implementation details
+}
+```
+
+**Benefits:**
+- Benefit 1
+- Benefit 2
+- Benefit 3
+
+**Trade-offs:**
+- Consider 1
+- Consider 2
+- Consider 3
+
+### Pattern 2: Advanced Technique
+
+**Description:**
+Another important pattern for code reviewer.
+
+**Implementation:**
+```typescript
+// Advanced example
+async function advancedExample() {
+  // Code here
+}
+```
+
+## Guidelines
+
+### Code Organization
+- Clear structure
+- Logical separation
+- Consistent naming
+- Proper documentation
+
+### Performance Considerations
+- Optimization strategies
+- Bottleneck identification
+- Monitoring approaches
+- Scaling techniques
+
+### Security Best Practices
+- Input validation
+- Authentication
+- Authorization
+- Data protection
+
+## Common Patterns
+
+### Pattern A
+Implementation details and examples.
+
+### Pattern B
+Implementation details and examples.
+
+### Pattern C
+Implementation details and examples.
+
+## Anti-Patterns to Avoid
+
+### Anti-Pattern 1
+What not to do and why.
+
+### Anti-Pattern 2
+What not to do and why.
+
+## Tools and Resources
+
+### Recommended Tools
+- Tool 1: Purpose
+- Tool 2: Purpose
+- Tool 3: Purpose
+
+### Further Reading
+- Resource 1
+- Resource 2
+- Resource 3
+
+## Conclusion
+
+Key takeaways for using this reference guide effectively.

package/.claude/skills/code-reviewer/references/coding_standards.md

@@ -0,0 +1,103 @@
+# Coding Standards
+
+## Overview
+
+This reference guide provides comprehensive information for code reviewer.
+
+## Patterns and Practices
+
+### Pattern 1: Best Practice Implementation
+
+**Description:**
+Detailed explanation of the pattern.
+
+**When to Use:**
+- Scenario 1
+- Scenario 2
+- Scenario 3
+
+**Implementation:**
+```typescript
+// Example code implementation
+export class Example {
+  // Implementation details
+}
+```
+
+**Benefits:**
+- Benefit 1
+- Benefit 2
+- Benefit 3
+
+**Trade-offs:**
+- Consider 1
+- Consider 2
+- Consider 3
+
+### Pattern 2: Advanced Technique
+
+**Description:**
+Another important pattern for code reviewer.
+
+**Implementation:**
+```typescript
+// Advanced example
+async function advancedExample() {
+  // Code here
+}
+```
+
+## Guidelines
+
+### Code Organization
+- Clear structure
+- Logical separation
+- Consistent naming
+- Proper documentation
+
+### Performance Considerations
+- Optimization strategies
+- Bottleneck identification
+- Monitoring approaches
+- Scaling techniques
+
+### Security Best Practices
+- Input validation
+- Authentication
+- Authorization
+- Data protection
+
+## Common Patterns
+
+### Pattern A
+Implementation details and examples.
+
+### Pattern B
+Implementation details and examples.
+
+### Pattern C
+Implementation details and examples.
+
+## Anti-Patterns to Avoid
+
+### Anti-Pattern 1
+What not to do and why.
+
+### Anti-Pattern 2
+What not to do and why.
+
+## Tools and Resources
+
+### Recommended Tools
+- Tool 1: Purpose
+- Tool 2: Purpose
+- Tool 3: Purpose
+
+### Further Reading
+- Resource 1
+- Resource 2
+- Resource 3
+
+## Conclusion
+
+Key takeaways for using this reference guide effectively.