claude-code-orchestrator-kit 1.4.0 → 1.4.15

package/.claude/commands/health-reuse.md

@@ -1,327 +1,30 @@
 ---
-description: Code reuse detection and consolidation workflow with full cycle management
+description: Code duplication detection and consolidation workflow (inline orchestration)
 ---
 
 # Code Reuse Health Check
 
-> **PATTERN**: Agent-based orchestration (see `docs/Agents Ecosystem/AGENT-ORCHESTRATION.md` for details)
+Execute the `reuse-health-inline` skill for inline orchestration.
 
-Complete code duplication detection and consolidation workflow with orchestrator-worker coordination.
+**You ARE the orchestrator.** Do not spawn a separate orchestrator agent.
 
-**What it does:**
-- Full duplication detection (types, schemas, constants, utilities)
-- Staged consolidation (HIGH → MEDIUM → LOW priority)
-- Quality gates after each stage
-- Verification scan
-- Up to 3 iterations if issues remain
-- Comprehensive final report
+## Quick Start
 
-**No configuration needed** - runs comprehensive checks always.
+1. Read `.claude/skills/reuse-health-inline/SKILL.md`
+2. Follow the workflow phases directly
+3. Use Task tool only for workers (reuse-hunter, reuse-fixer)
+4. Run quality gates inline via Bash
 
----
-
-## Your Task
-
-### Step 1: Phase 0 - Invoke Orchestrator (Pre-flight)
-
-Use Task tool to invoke reuse-orchestrator for pre-flight validation:
+## Workflow Summary
 
 ```
-subagent_type: "reuse-orchestrator"
-description: "Reuse orchestrator pre-flight"
-prompt: "Execute Phase 0: Pre-flight Validation
-
-Tasks:
-1. Validate environment (package.json, scripts, git status)
-2. Initialize progress tracking via TodoWrite
-3. Initialize iteration tracking (iteration=1, max=3)
-4. Create .tmp/current/plans/reuse-detection.json for rollback tracking
-5. Report pre-flight status
-
-IMPORTANT: After completing pre-flight, create .tmp/current/plans/reuse-detection.json and return control to main session.
-
-Return the following information:
-- Pre-flight status (✅/⛔)
-- Environment validation results
-- Plan file path created
-- Ready for next phase: true/false
-"
+Pre-flight → Detect → [Consolidate by Priority] → Verify → Report
 ```
 
-**Then**: Wait for orchestrator to return.
+**Workers**: reuse-hunter, reuse-fixer
+**Quality gates**: `pnpm type-check && pnpm build`
+**Max iterations**: 3
 
 ---
 
-### Step 2: Phase 1 - Invoke reuse-hunter (Detection)
-
-After orchestrator returns:
-
-1. **Read plan file** to confirm it was created:
-   ```
-   Use Read tool: .tmp/current/plans/reuse-detection.json
-   Verify nextAgent === "reuse-hunter"
-   ```
-
-2. **Invoke reuse-hunter** using Task tool:
-   ```
-   subagent_type: "reuse-hunter"
-   description: "Code duplication detection phase"
-   prompt: "Execute code duplication detection based on plan file: .tmp/current/plans/reuse-detection.json
-
-Read the plan file and execute comprehensive duplication detection:
-- Scan entire codebase for duplicated types, interfaces, Zod schemas
-- Find duplicated constants and configuration objects
-- Identify utility functions that are copied instead of imported
-- Categorize by priority (HIGH → MEDIUM → LOW)
-- Generate reuse-hunting-report.md
-
-Return to main session when complete."
-   ```
-
-**Then**: Wait for reuse-hunter to return with report.
-
----
-
-### Step 3: Quality Gate 1 - Resume Orchestrator (Validate Detection)
-
-After reuse-hunter returns:
-
-1. **Resume orchestrator** for validation using Task tool:
-   ```
-   subagent_type: "reuse-orchestrator"
-   description: "Validate duplication detection"
-   prompt: "Execute Quality Gate 1: Detection Validation
-
-Phase: Validate reuse-hunter output
-
-Tasks:
-1. Verify reuse-hunting-report.md exists
-2. Validate report structure (required sections)
-3. Parse duplication counts by priority
-4. Run type-check validation (non-blocking warning)
-5. Report gate results
-
-IMPORTANT: After validation, if duplications found:
-- Create .tmp/current/plans/reuse-consolidation-{priority}.json for highest priority
-- Return control to main session
-
-If no duplications found or all gates fail:
-- Skip to final summary
-- Return control
-
-Return the following:
-- Gate status (✅ PASSED / ⛔ FAILED / ⚠️ WARNINGS)
-- Duplication counts by priority
-- Next phase: consolidation-high / consolidation-medium / final-summary
-- Plan file created (if applicable)
-"
-   ```
-
-**Then**: Wait for orchestrator validation results.
-
----
-
-### Step 4: Phase 2-4 - Consolidation Stages (Iterative)
-
-After orchestrator returns with consolidation plan:
-
-**For each priority level** (HIGH → MEDIUM → LOW):
-
-1. **Check if this priority has duplications**:
-   - Read orchestrator response
-   - If orchestrator says "skip to next priority" → continue loop
-   - If orchestrator says "final summary" → go to Step 5
-
-2. **Read consolidation plan**:
-   ```
-   Use Read tool: .tmp/current/plans/reuse-consolidation-{priority}.json
-   Verify nextAgent === "reuse-fixer"
-   Verify config.priority === "{current-priority}"
-   ```
-
-3. **Invoke reuse-fixer** using Task tool:
-   ```
-   subagent_type: "reuse-fixer"
-   description: "Consolidate {priority} duplications"
-   prompt: "Execute code consolidation based on plan file: .tmp/current/plans/reuse-consolidation-{priority}.json
-
-Read the plan file and consolidate duplications for priority: {priority}
-- Read reuse-hunting-report.md for duplication list
-- For each duplication:
-  - Determine canonical location (usually shared-types)
-  - Create/update canonical file
-  - Replace duplicates with re-exports
-- Log changes to .reuse-changes.json
-- Update reuse-consolidation-implemented.md (consolidated report)
-
-Return to main session when complete."
-   ```
-
-4. **Resume orchestrator** for validation:
-   ```
-   subagent_type: "reuse-orchestrator"
-   description: "Validate {priority} consolidation"
-   prompt: "Execute Quality Gate 2: Consolidation Validation for priority={priority}
-
-Tasks:
-1. Verify reuse-consolidation-implemented.md exists
-2. Run type-check (BLOCKING)
-3. Run build (BLOCKING)
-4. Parse consolidation success rate
-5. Check if retry needed (if < 80% success)
-
-If validation PASSES and more priorities remain:
-- Create next .tmp/current/plans/reuse-consolidation-{priority}.json
-- Return control
-
-If validation FAILS:
-- Provide rollback instructions
-- Return control with error
-
-If all priorities complete:
-- Proceed to verification phase
-- Return control
-
-Return:
-- Gate status
-- Consolidation success rate
-- Next phase: consolidation-{next-priority} / verification / final-summary
-"
-   ```
-
-5. **Repeat** for next priority level.
-
----
-
-### Step 5: Phase 5 - Verification
-
-After all consolidation stages complete:
-
-1. **Resume orchestrator** for verification:
-   ```
-   subagent_type: "reuse-orchestrator"
-   description: "Create verification plan"
-   prompt: "Execute Phase 5: Verification Preparation
-
-Create .tmp/current/plans/reuse-verification.json for re-scanning codebase.
-
-Return control with plan file path."
-   ```
-
-2. **Invoke reuse-hunter** for verification:
-   ```
-   subagent_type: "reuse-hunter"
-   description: "Verification scan"
-   prompt: "Execute verification scan based on: .tmp/current/plans/reuse-verification.json
-
-Re-scan codebase to verify consolidations. Overwrites reuse-hunting-report.md.
-
-Return when complete."
-   ```
-
-3. **Resume orchestrator** for verification validation:
-   ```
-   subagent_type: "reuse-orchestrator"
-   description: "Validate verification"
-   prompt: "Execute Quality Gate 3: Verification Validation
-
-Compare original reuse-hunting-report.md (baseline) with new scan:
-- Count duplications resolved
-- Check if new duplications introduced
-- Determine if iteration needed
-
-Return:
-- Verification status
-- Duplications remaining
-- Iteration decision: iterate / complete
-"
-   ```
-
----
-
-### Step 6: Final Summary
-
-After all phases complete:
-
-1. **Resume orchestrator** for final summary:
-   ```
-   subagent_type: "reuse-orchestrator"
-   description: "Generate final summary"
-   prompt: "Execute Phase 7: Final Summary
-
-Generate comprehensive reuse-orchestration-summary.md:
-- All duplications detected
-- All consolidations performed
-- Success rates by priority
-- Validation results
-- Iteration summary
-- Cleanup instructions
-
-Return final summary."
-   ```
-
-2. **Display results** to user:
-   ```
-   Read reuse-orchestration-summary.md
-   Display key metrics
-   Show validation status
-   List next steps
-   ```
-
----
-
-## Example Usage
-
-```bash
-# Run complete code reuse workflow
-/health-reuse
-```
-
----
-
-## Architecture Notes
-
-**Orchestrator Role**:
-- Creates plan files
-- Validates worker outputs
-- Returns control to main session
-- NO direct worker invocation
-
-**Main Session Role** (this command):
-- Reads plan files
-- Invokes workers via Task tool
-- Resumes orchestrator for validation
-- Manages full cycle
-
-**Worker Role**:
-- Reads plan file
-- Executes work
-- Generates report
-- Returns to main session
-
-This pattern follows Claude Code's actual capabilities (no auto-invoke).
-
----
-
-## Duplication Categories
-
-**Types/Interfaces** (shared-types):
-- Database types
-- API types
-- Zod schemas
-- Common enums
-
-**Constants** (shared-types):
-- Configuration objects
-- MIME types, file limits
-- Feature flags
-
-**Utilities** (shared package or re-export):
-- Helper functions
-- Validation utilities
-- Formatters
-
-**Single Source of Truth Pattern**:
-1. Canonical location: `packages/shared-types/src/`
-2. Other packages: `export * from '@megacampus/shared-types/{module}'`
-3. NEVER copy code between packages
+Now read and execute the skill: `.claude/skills/reuse-health-inline/SKILL.md`

package/.claude/commands/health-security.md

@@ -1,297 +1,30 @@
 ---
-description: Security vulnerability detection and remediation workflow with full cycle management
+description: Security vulnerability detection and remediation workflow (inline orchestration)
 ---
 
 # Security Health Check
 
-> **PATTERN**: Agent-based orchestration (see `docs/Agents Ecosystem/AGENT-ORCHESTRATION.md` for details)
+Execute the `security-health-inline` skill for inline orchestration.
 
-Complete security scanning and vulnerability fixing workflow with orchestrator-worker coordination.
+**You ARE the orchestrator.** Do not spawn a separate orchestrator agent.
 
-**What it does:**
-- Full security scan (SQL injection, XSS, auth issues, RLS policies, secrets)
-- Staged fixing (critical → high → medium → low)
-- Quality gates after each stage
-- Verification scan
-- Up to 3 iterations if issues remain
-- Comprehensive final report
+## Quick Start
 
-**No configuration needed** - runs comprehensive security audit always.
+1. Read `.claude/skills/security-health-inline/SKILL.md`
+2. Follow the workflow phases directly
+3. Use Task tool only for workers (security-scanner, vulnerability-fixer)
+4. Run quality gates inline via Bash
 
----
-
-## Your Task
-
-### Step 1: Phase 0 - Invoke Orchestrator (Pre-flight)
-
-Use Task tool to invoke security-orchestrator for pre-flight validation:
+## Workflow Summary
 
 ```
-subagent_type: "security-orchestrator"
-description: "Security orchestrator pre-flight"
-prompt: "Execute Phase 0: Pre-flight Validation
-
-Tasks:
-1. Validate environment (package.json, scripts, git status)
-2. Initialize progress tracking via TodoWrite
-3. Initialize iteration tracking (iteration=1, max=3)
-4. Create .tmp/current/plans/security-detection.json for rollback tracking
-5. Report pre-flight status
-
-IMPORTANT: After completing pre-flight, create .tmp/current/plans/security-detection.json and return control to main session.
-
-Return the following information:
-- Pre-flight status (✅/⛔)
-- Environment validation results
-- Plan file path created
-- Ready for next phase: true/false
-"
+Pre-flight → Detect → [Fix by Priority] → Verify → Report
 ```
 
-**Then**: Wait for orchestrator to return.
-
----
-
-### Step 2: Phase 1 - Invoke security-scanner (Detection)
-
-After orchestrator returns:
-
-1. **Read plan file** to confirm it was created:
-   ```
-   Use Read tool: .tmp/current/plans/security-detection.json
-   Verify nextAgent === "security-scanner"
-   ```
-
-2. **Invoke security-scanner** using Task tool:
-   ```
-   subagent_type: "security-scanner"
-   description: "Security detection phase"
-   prompt: "Execute vulnerability detection based on plan file: .tmp/current/plans/security-detection.json
-
-Read the plan file and execute comprehensive vulnerability detection:
-- Scan entire codebase
-- Categorize by priority (critical → high → medium → low)
-- Generate security-scan-report.md
-
-Return to main session when complete."
-   ```
-
-**Then**: Wait for security-scanner to return with report.
-
----
-
-### Step 3: Quality Gate 1 - Resume Orchestrator (Validate Detection)
-
-After security-scanner returns:
-
-1. **Resume orchestrator** for validation using Task tool:
-   ```
-   subagent_type: "security-orchestrator"
-   description: "Validate vulnerability detection"
-   prompt: "Execute Quality Gate 1: Detection Validation
-
-Phase: Validate security-scanner output
-
-Tasks:
-1. Verify security-scan-report.md exists
-2. Validate report structure (required sections)
-3. Parse vulnerability counts by priority
-4. Run type-check validation (non-blocking warning)
-5. Report gate results
-
-IMPORTANT: After validation, if vulnerabilitys found:
-- Create .tmp/current/plans/security-fixing-{priority}.json for critical priority (or highest available)
-- Return control to main session
-
-If no vulnerabilitys found or all gates fail:
-- Skip to final summary
-- Return control
-
-Return the following:
-- Gate status (✅ PASSED / ⛔ FAILED / ⚠️ WARNINGS)
-- Security counts by priority
-- Next phase: fixing-critical / fixing-high / final-summary
-- Plan file created (if applicable)
-"
-   ```
-
-**Then**: Wait for orchestrator validation results.
-
----
-
-### Step 4: Phase 2-5 - Fixing Stages (Iterative)
-
-After orchestrator returns with fixing plan:
-
-**For each priority level** (critical → high → medium → low):
-
-1. **Check if this priority has vulnerabilitys**:
-   - Read orchestrator response
-   - If orchestrator says "skip to next priority" → continue loop
-   - If orchestrator says "final summary" → go to Step 5
-
-2. **Read fixing plan**:
-   ```
-   Use Read tool: .tmp/current/plans/security-fixing-{priority}.json
-   Verify nextAgent === "vulnerability-fixer"
-   Verify config.priority === "{current-priority}"
-   ```
-
-3. **Invoke vulnerability-fixer** using Task tool:
-   ```
-   subagent_type: "vulnerability-fixer"
-   description: "Fix {priority} vulnerabilitys"
-   prompt: "Execute vulnerability fixing based on plan file: .tmp/current/plans/security-fixing-{priority}.json
-
-Read the plan file and fix vulnerabilitys for priority: {priority}
-- Read security-scan-report.md for vulnerability list
-- Fix vulnerabilitys one by one
-- Log changes to .vulnerability-changes.json
-- Update security-fixes-implemented.md (consolidated report)
-
-Return to main session when complete."
-   ```
-
-4. **Resume orchestrator** for validation:
-   ```
-   subagent_type: "security-orchestrator"
-   description: "Validate {priority} fixes"
-   prompt: "Execute Quality Gate 2: Fixes Validation for priority={priority}
-
-Tasks:
-1. Verify security-fixes-implemented.md exists
-2. Run type-check (BLOCKING)
-3. Run build (BLOCKING)
-4. Parse fix success rate
-5. Check if retry needed (if < 80% success)
-
-If validation PASSES and more priorities remain:
-- Create next .tmp/current/plans/security-fixing-{priority}.json
-- Return control
-
-If validation FAILS:
-- Provide rollback instructions
-- Return control with error
-
-If all priorities complete:
-- Proceed to verification phase
-- Return control
-
-Return:
-- Gate status
-- Fix success rate
-- Next phase: fixing-{next-priority} / verification / final-summary
-"
-   ```
-
-5. **Repeat** for next priority level.
+**Workers**: security-scanner, vulnerability-fixer
+**Quality gates**: `pnpm type-check && pnpm build`
+**Max iterations**: 3
 
 ---
 
-### Step 5: Phase 6 - Verification
-
-After all fixing stages complete:
-
-1. **Resume orchestrator** for verification:
-   ```
-   subagent_type: "security-orchestrator"
-   description: "Create verification plan"
-   prompt: "Execute Phase 6: Verification Preparation
-
-Create .tmp/current/plans/security-verification.json for re-scanning codebase.
-
-Return control with plan file path."
-   ```
-
-2. **Invoke security-scanner** for verification:
-   ```
-   subagent_type: "security-scanner"
-   description: "Verification scan"
-   prompt: "Execute verification scan based on: .tmp/current/plans/security-verification.json
-
-Re-scan codebase to verify fixes. Overwrites security-scan-report.md.
-
-Return when complete."
-   ```
-
-3. **Resume orchestrator** for verification validation:
-   ```
-   subagent_type: "security-orchestrator"
-   description: "Validate verification"
-   prompt: "Execute Quality Gate 3: Verification Validation
-
-Compare original security-scan-report.md (baseline) with new scan:
-- Count vulnerabilitys fixed
-- Check if new vulnerabilitys introduced
-- Determine if iteration needed
-
-Return:
-- Verification status
-- Securitys remaining
-- Iteration decision: iterate / complete
-"
-   ```
-
----
-
-### Step 6: Final Summary
-
-After all phases complete:
-
-1. **Resume orchestrator** for final summary:
-   ```
-   subagent_type: "security-orchestrator"
-   description: "Generate final summary"
-   prompt: "Execute Phase 8: Final Summary
-
-Generate comprehensive security-orchestration-summary.md:
-- All vulnerabilitys detected
-- All vulnerabilitys fixed
-- Success rates by priority
-- Validation results
-- Iteration summary
-- Cleanup instructions
-
-Return final summary."
-   ```
-
-2. **Display results** to user:
-   ```
-   Read security-orchestration-summary.md
-   Display key metrics
-   Show validation status
-   List next steps
-   ```
-
----
-
-## Example Usage
-
-```bash
-# Run complete vulnerability workflow
-/health-vulnerabilitys
-```
-
----
-
-## Architecture Notes
-
-**Orchestrator Role**:
-- Creates plan files
-- Validates worker outputs
-- Returns control to main session
-- NO direct worker invocation
-
-**Main Session Role** (this command):
-- Reads plan files
-- Invokes workers via Task tool
-- Resumes orchestrator for validation
-- Manages full cycle
-
-**Worker Role**:
-- Reads plan file
-- Executes work
-- Generates report
-- Returns to main session
-
-This pattern follows Claude Code's actual capabilities (no auto-invoke).
+Now read and execute the skill: `.claude/skills/security-health-inline/SKILL.md`

package/.claude/commands/push.md

@@ -1,6 +1,6 @@
 ---
-description: Automated release management with version bumping and changelog updates
-argument-hint: [patch|minor|major]
+description: Automated release management with version bumping and dual changelog generation
+argument-hint: [patch|minor|major] [-m "message"]
 ---
 
 Execute the release automation script with auto-confirmation for Claude Code.
@@ -9,10 +9,24 @@ Execute the release automation script with auto-confirmation for Claude Code.
 - Auto-syncs package.json versions with latest git tag (prevents version conflicts)
 - Analyzes commits since last release
 - Auto-detects version bump type from conventional commits
-- Generates CHANGELOG entries
+- **Generates dual changelogs:**
+  - `CHANGELOG.md` - Technical format (Keep a Changelog) for developers
+  - `RELEASE_NOTES.md` - User-facing format with friendly language for marketing
 - Updates all package.json files
 - Creates git tag and pushes to GitHub
 - Full rollback support on errors
+- **Custom commit message** for uncommitted changes via `--message` / `-m` flag
+
+**Generated RELEASE_NOTES.md format:**
+- Friendly scope names (auth → Authentication, db → Database)
+- Emojis for visual clarity (✨ Features, 🐛 Fixes, 🔒 Security)
+- Skips technical commits (chore, ci, docs) not relevant to users
+- Ready to copy for announcements, app stores, emails
+
+**Tip:** Use `-m` with `feat:` or `fix:` prefix to include your changes in RELEASE_NOTES:
+```bash
+/push patch -m "feat(worker): add worker readiness pre-flight system"
+```
 
 **Usage:**