claude-code-orchestrator-kit 1.0.0

package/.claude/skills/parse-git-status/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: parse-git-status
+description: Parse git status output into structured data showing staged, modified, and untracked files. Use for pre-flight validation, checking clean working directory, or listing changed files before commits.
+---
+
+# Parse Git Status
+
+Parse git status command output into structured JSON for programmatic analysis.
+
+## When to Use
+
+- Pre-flight checks before workflow execution
+- Validate clean working directory
+- List modified files for commit
+- Check for uncommitted changes
+
+## Instructions
+
+### Step 1: Receive Git Status Output
+
+Accept raw git status output as input.
+
+**Expected Input**:
+- `gitStatusOutput`: String (raw output from `git status --porcelain` or regular `git status`)
+
+### Step 2: Parse Branch Information
+
+Extract current branch and tracking information.
+
+**Patterns**:
+- `## branch-name`: Current branch
+- `## branch-name...origin/branch-name`: Tracking branch
+- `[ahead N]` or `[behind N]`: Ahead/behind commits
+
+### Step 3: Categorize Files
+
+Parse file status indicators and categorize.
+
+**Status Indicators** (porcelain format):
+- `M `: Modified (staged)
+- ` M`: Modified (unstaged)
+- `A `: Added (staged)
+- `D `: Deleted (staged)
+- `R `: Renamed (staged)
+- `??`: Untracked
+- `!!`: Ignored
+
+### Step 4: Return Structured Data
+
+Return parsed data as JSON object.
+
+**Expected Output**:
+```json
+{
+  "branch": "main",
+  "tracking": "origin/main",
+  "ahead": 0,
+  "behind": 0,
+  "staged": ["file1.ts", "file2.ts"],
+  "modified": ["file3.ts"],
+  "deleted": [],
+  "renamed": [],
+  "untracked": ["file4.ts"],
+  "clean": false
+}
+```
+
+## Error Handling
+
+- **Invalid Git Output**: Return error describing format issue
+- **Not a Git Repository**: Return error indicating no git repo
+- **Empty Output**: Return clean status with empty arrays
+
+## Examples
+
+### Example 1: Clean Working Directory
+
+**Input**:
+```
+On branch main
+Your branch is up to date with 'origin/main'.
+
+nothing to commit, working tree clean
+```
+
+**Output**:
+```json
+{
+  "branch": "main",
+  "tracking": "origin/main",
+  "ahead": 0,
+  "behind": 0,
+  "staged": [],
+  "modified": [],
+  "deleted": [],
+  "renamed": [],
+  "untracked": [],
+  "clean": true
+}
+```
+
+### Example 2: Modified Files
+
+**Input** (porcelain format):
+```
+## main...origin/main [ahead 2]
+M  src/utils.ts
+ M src/types.ts
+A  src/new-feature.ts
+?? temp-file.js
+```
+
+**Output**:
+```json
+{
+  "branch": "main",
+  "tracking": "origin/main",
+  "ahead": 2,
+  "behind": 0,
+  "staged": ["src/utils.ts", "src/new-feature.ts"],
+  "modified": ["src/types.ts"],
+  "deleted": [],
+  "renamed": [],
+  "untracked": ["temp-file.js"],
+  "clean": false
+}
+```
+
+### Example 3: Detached HEAD
+
+**Input**:
+```
+## HEAD (no branch)
+ M README.md
+```
+
+**Output**:
+```json
+{
+  "branch": "HEAD (detached)",
+  "tracking": null,
+  "ahead": 0,
+  "behind": 0,
+  "staged": [],
+  "modified": ["README.md"],
+  "deleted": [],
+  "renamed": [],
+  "untracked": [],
+  "clean": false
+}
+```
+
+## Validation
+
+- [ ] Parses branch information correctly
+- [ ] Categorizes files by status
+- [ ] Handles empty/clean status
+- [ ] Parses ahead/behind indicators
+- [ ] Handles detached HEAD state
+- [ ] Returns clean:true only when appropriate
+
+## Supporting Files
+
+None required - pure parsing logic.

package/.claude/skills/parse-package-json/SKILL.md

@@ -0,0 +1,151 @@
+---
+name: parse-package-json
+description: Extract version, dependencies, and metadata from package.json files. Use when needing project version, dependency list, or package metadata for releases, audits, or reports.
+allowed-tools: Read
+---
+
+# Parse Package JSON
+
+Extract structured data from package.json files for version management, dependency auditing, and metadata retrieval.
+
+## When to Use
+
+- Get current project version for release workflows
+- Extract dependency list for auditing
+- Read package metadata for reports
+- Validate package.json structure
+
+## Instructions
+
+### Step 1: Read package.json
+
+Use Read tool to load package.json file.
+
+**Expected Input**:
+- `file_path`: Path to package.json (default: `./package.json`)
+
+**Tools Used**: Read
+
+### Step 2: Parse JSON
+
+Parse the JSON content and validate structure.
+
+**Validation**:
+- File must be valid JSON
+- Must contain `name` and `version` fields at minimum
+- Dependencies should be objects (if present)
+
+### Step 3: Extract Fields
+
+Extract relevant fields into structured output.
+
+**Fields to Extract**:
+- `version`: Semantic version string
+- `name`: Package name
+- `description`: Package description (optional)
+- `dependencies`: Production dependencies object (optional)
+- `devDependencies`: Development dependencies object (optional)
+- `scripts`: Available npm scripts (optional)
+- `main`: Entry point file (optional)
+- `private`: Private flag (optional)
+
+### Step 4: Return Structured Data
+
+Return extracted data as JSON object.
+
+**Expected Output**:
+```json
+{
+  "version": "0.7.0",
+  "name": "megacampus2",
+  "description": "Project description",
+  "dependencies": {
+    "react": "^18.2.0"
+  },
+  "devDependencies": {
+    "typescript": "^5.0.0"
+  },
+  "scripts": {
+    "build": "tsc",
+    "test": "jest"
+  },
+  "main": "dist/index.js",
+  "private": true
+}
+```
+
+## Error Handling
+
+- **File Not Found**: Return error with message "package.json not found at {path}"
+- **Invalid JSON**: Return error with parsing details
+- **Missing Required Fields**: Return error listing missing fields (name, version)
+- **Invalid Structure**: Return error describing structure issue
+
+## Examples
+
+### Example 1: Extract Version
+
+**Input**:
+```
+file_path: ./package.json
+```
+
+**Output**:
+```json
+{
+  "version": "0.7.0",
+  "name": "megacampus2"
+}
+```
+
+### Example 2: Full Package Info
+
+**Input**:
+```
+file_path: ./packages/client/package.json
+```
+
+**Output**:
+```json
+{
+  "version": "1.2.3",
+  "name": "@megacampus/client",
+  "dependencies": {
+    "react": "^18.2.0",
+    "react-dom": "^18.2.0"
+  },
+  "scripts": {
+    "dev": "vite",
+    "build": "vite build"
+  }
+}
+```
+
+### Example 3: Error - File Not Found
+
+**Input**:
+```
+file_path: ./nonexistent.json
+```
+
+**Output**:
+```json
+{
+  "error": "package.json not found at ./nonexistent.json",
+  "success": false
+}
+```
+
+## Validation
+
+- [ ] Can read package.json from default path
+- [ ] Can read package.json from custom path
+- [ ] Extracts all specified fields correctly
+- [ ] Handles missing optional fields gracefully
+- [ ] Returns error for missing file
+- [ ] Returns error for invalid JSON
+- [ ] Returns error for missing required fields
+
+## Supporting Files
+
+- `schema.json`: JSON schema defining expected package.json structure

package/.claude/skills/parse-package-json/schema.json

@@ -0,0 +1,43 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "package.json Schema",
+  "type": "object",
+  "required": ["name", "version"],
+  "properties": {
+    "name": {
+      "type": "string",
+      "pattern": "^(@[a-z0-9-~][a-z0-9-._~]*/)?[a-z0-9-~][a-z0-9-._~]*$"
+    },
+    "version": {
+      "type": "string",
+      "pattern": "^\\d+\\.\\d+\\.\\d+(-[a-zA-Z0-9.-]+)?(\\+[a-zA-Z0-9.-]+)?$"
+    },
+    "description": {
+      "type": "string"
+    },
+    "main": {
+      "type": "string"
+    },
+    "private": {
+      "type": "boolean"
+    },
+    "scripts": {
+      "type": "object",
+      "additionalProperties": {
+        "type": "string"
+      }
+    },
+    "dependencies": {
+      "type": "object",
+      "additionalProperties": {
+        "type": "string"
+      }
+    },
+    "devDependencies": {
+      "type": "object",
+      "additionalProperties": {
+        "type": "string"
+      }
+    }
+  }
+}

package/.claude/skills/render-template/SKILL.md

@@ -0,0 +1,245 @@
+---
+name: render-template
+description: Render templates with variable substitution using {{variable}} or ${variable} syntax. Use for generating formatted output, reports, commit messages, or any text requiring variable interpolation.
+---
+
+# Render Template
+
+Render templates with variable substitution, supporting various syntax formats and helper functions.
+
+## When to Use
+
+- Format commit messages with dynamic data
+- Generate report sections with variables
+- Create formatted outputs from templates
+- Replace placeholders in text templates
+- Consolidate formatting logic across Skills
+
+## Instructions
+
+### Step 1: Receive Template and Data
+
+Accept template string and variable data.
+
+**Expected Input**:
+- `template`: String (template with placeholders)
+- `variables`: Object (key-value pairs for substitution)
+- `syntax`: String (optional: mustache|shell|mixed, default: mustache)
+
+**Supported Syntax**:
+- **Mustache**: `{{variable}}`, `{{object.property}}`
+- **Shell**: `${variable}`, `${VARIABLE}`
+- **Mixed**: Supports both
+
+### Step 2: Parse Template
+
+Identify all placeholders in template.
+
+**Placeholder Patterns**:
+- `{{variable}}`: Simple variable
+- `{{object.property}}`: Nested property
+- `{{#if condition}}...{{/if}}`: Conditional (optional)
+- `{{#each array}}...{{/each}}`: Loop (optional)
+
+### Step 3: Resolve Variables
+
+Replace placeholders with values from variables object.
+
+**Resolution Rules**:
+- Direct match: `{{name}}` → `variables.name`
+- Nested property: `{{user.name}}` → `variables.user.name`
+- Missing variable: Replace with empty string or keep placeholder (configurable)
+- Undefined: Replace with empty string
+
+### Step 4: Apply Filters (Optional)
+
+Support simple filters if specified.
+
+**Common Filters**:
+- `{{variable | uppercase}}`: Convert to uppercase
+- `{{variable | lowercase}}`: Convert to lowercase
+- `{{variable | capitalize}}`: Capitalize first letter
+- `{{date | format:YYYY-MM-DD}}`: Format date
+
+### Step 5: Return Rendered Output
+
+Return final rendered string.
+
+**Expected Output**: String (template with variables replaced)
+
+## Error Handling
+
+- **Missing Variables**: Replace with empty string or warn (configurable)
+- **Invalid Template Syntax**: Return error describing syntax issue
+- **Circular References**: Detect and return error
+- **Type Mismatch**: Convert to string automatically
+
+## Examples
+
+### Example 1: Simple Variable Substitution
+
+**Input**:
+```json
+{
+  "template": "Hello {{name}}, your score is {{score}}!",
+  "variables": {
+    "name": "Alice",
+    "score": 95
+  },
+  "syntax": "mustache"
+}
+```
+
+**Output**:
+```
+Hello Alice, your score is 95!
+```
+
+### Example 2: Nested Properties
+
+**Input**:
+```json
+{
+  "template": "User: {{user.name}} ({{user.email}})\nRole: {{user.role}}",
+  "variables": {
+    "user": {
+      "name": "Bob",
+      "email": "bob@example.com",
+      "role": "admin"
+    }
+  }
+}
+```
+
+**Output**:
+```
+User: Bob (bob@example.com)
+Role: admin
+```
+
+### Example 3: Shell Syntax
+
+**Input**:
+```json
+{
+  "template": "Version: ${VERSION}\nDate: ${RELEASE_DATE}",
+  "variables": {
+    "VERSION": "0.8.0",
+    "RELEASE_DATE": "2025-10-17"
+  },
+  "syntax": "shell"
+}
+```
+
+**Output**:
+```
+Version: 0.8.0
+Date: 2025-10-17
+```
+
+### Example 4: Commit Message Template
+
+**Input**:
+```json
+{
+  "template": "{{type}}({{scope}}): {{description}}\n\n{{body}}\n\n🤖 Generated with Claude Code\nCo-Authored-By: Claude <noreply@anthropic.com>",
+  "variables": {
+    "type": "feat",
+    "scope": "auth",
+    "description": "add OAuth2 support",
+    "body": "Implemented OAuth2 flow with token refresh.\nSupports Google and GitHub providers."
+  }
+}
+```
+
+**Output**:
+```
+feat(auth): add OAuth2 support
+
+Implemented OAuth2 flow with token refresh.
+Supports Google and GitHub providers.
+
+🤖 Generated with Claude Code
+Co-Authored-By: Claude <noreply@anthropic.com>
+```
+
+### Example 5: Missing Variables
+
+**Input**:
+```json
+{
+  "template": "Name: {{name}}\nAge: {{age}}\nCity: {{city}}",
+  "variables": {
+    "name": "Alice"
+  }
+}
+```
+
+**Output (with empty string replacement)**:
+```
+Name: Alice
+Age:
+City:
+```
+
+**Output (with keep placeholder)**:
+```
+Name: Alice
+Age: {{age}}
+City: {{city}}
+```
+
+### Example 6: Report Header Template
+
+**Input**:
+```json
+{
+  "template": "# {{reportType}} Report: {{version}}\n\n**Generated**: {{timestamp}}\n**Status**: {{statusEmoji}} {{status}}\n**Version**: {{version}}",
+  "variables": {
+    "reportType": "Bug Hunting",
+    "version": "2025-10-17",
+    "timestamp": "2025-10-17 14:30:00 UTC",
+    "statusEmoji": "✅",
+    "status": "success"
+  }
+}
+```
+
+**Output**:
+```markdown
+# Bug Hunting Report: 2025-10-17
+
+**Generated**: 2025-10-17 14:30:00 UTC
+**Status**: ✅ success
+**Version**: 2025-10-17
+```
+
+## Validation
+
+- [ ] Replaces simple variables correctly
+- [ ] Handles nested properties
+- [ ] Supports multiple syntax formats
+- [ ] Handles missing variables gracefully
+- [ ] Converts types to strings
+- [ ] Preserves formatting (line breaks, indentation)
+- [ ] Detects circular references
+- [ ] Returns clear error messages
+
+## Supporting Files
+
+None required - pure template rendering logic.
+
+## Integration with Other Skills
+
+This Skill consolidates formatting logic used by:
+- **format-commit-message**: Use render-template for message formatting
+- **generate-report-header**: Use render-template for header generation
+- **format-todo-list**: Use render-template for activeForm generation
+- **generate-changelog**: Use render-template for section formatting
+
+**Example Integration**:
+```
+Instead of: Hard-coded string formatting in each Skill
+Use: render-template Skill with predefined templates
+Result: Consistent formatting, easier to maintain
+```