immacualate/claude-forge/skill-factory

# Uncommitted changes
git diff HEAD --name-only 2>/dev/null
 
# Recent commits on current branch
git log --oneline -20 2>/dev/null
 
# Branch diff from main
git diff main...HEAD --name-only 2>/dev/null

{
  "name": "pattern-name",
  "description": "What was done repeatedly",
  "files": ["path/a.ts", "path/b.ts"],
  "steps": ["Step1", "Step2", "Step3"],
  "step_count": 3
}

Session Analysis Complete
 
Candidate Patterns Found: N
 
1. [pattern-name] - "Description of what was done repeatedly"
   Files: path/a.ts, path/b.ts (N files)
   Steps: Step1 -> Step2 -> Step3
 
2. [pattern-name] - "Description"
   ...
 
Which patterns should become skills? (select or 'all')

bash $HOME/.claude/skills/skill-factory/scripts/scan-inventory.sh --scope all > /tmp/sf-manifest.json

python3 $HOME/.claude/skills/skill-factory/scripts/similarity-scorer.py \
  --candidate "<pattern description>" \
  --candidate-name "<pattern-name>" \
  --manifest /tmp/sf-manifest.json \
  --top 3

Similarity Check Results
 
Pattern: "pdf-batch-edit"
  Top match: nano-pdf (score: 0.72) -> MERGE
  Recommendation: Extend nano-pdf with batch operations
 
Pattern: "config-updater"
  Top match: init-project (score: 0.45) -> UPDATE
  Recommendation: Add config-update subsection to init-project
 
Pattern: "api-load-test"
  Top match: e2e (score: 0.24) -> CREATE
  Recommendation: Create new skill
 
Action for each pattern? (CREATE / UPDATE / MERGE / SKIP)

Blueprint: api-load-test
 
Type: Workflow
Scope: global (~/.claude/skills/)
Structure:
  api-load-test/
  ├── SKILL.md (~200 lines)
  │   ├── Frontmatter: name, description with triggers
  │   ├── Overview
  │   ├── Prerequisites
  │   ├── Workflow (4 steps)
  │   └── Output Format
  └── scripts/
      └── run-load-test.sh
 
Key sections:
  1. Target URL configuration
  2. Load profile definition
  3. Test execution
  4. Results analysis
 
Approve this blueprint? (y/n/edit)

UPDATE Blueprint: config-updater -> init-project
 
Target skill: ~/.claude/skills/init-project/SKILL.md
Action: Add subsection "## Config Update" with steps
Estimated diff: +20-40 lines in existing SKILL.md

MERGE Blueprint: pdf-batch-edit -> nano-pdf
 
Target skill: ~/.claude/skills/nano-pdf/SKILL.md
Sections to add: "## Batch Operations" (new workflow section)
Scripts to add: scripts/batch-process.sh
Estimated diff: +60-100 lines in SKILL.md, +1 script

[ "${CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS:-0}" = "1" ] && echo "teams" || echo "no-team"

TeamCreate -> "skill-factory-run"
 
TaskCreate -> tami's analysis tasks (T1-T6)
TaskCreate -> jiwon's creation tasks (T7-T12, blocked by T6)
TaskCreate -> duri's validation tasks (T13-T18, blocked by T12)
 
Task -> tami (Explore, sonnet, blue)
  "Analyze session, run scan-inventory.sh, run similarity-scorer.py, report findings"
 
Task -> jiwon (general-purpose, sonnet, green)
  "For CREATE: read skill-templates.md, create SKILL.md + resources based on blueprint"
  "For UPDATE/MERGE: read target skill, apply diff from blueprint, add new sections/scripts"
 
Task -> duri (general-purpose, sonnet, yellow)
  "Run validate-skill.sh, verify triggers, register skill"

DRY RUN COMPLETE
 
Patterns analyzed: N
Decisions: X CREATE, Y MERGE, Z SKIP
Blueprints generated: X
 
No files were created. Remove --dry-run to execute.

Skill Factory Report
 
Session: <branch-name or "main">
Patterns found: N
Patterns processed: M
 
Results:
  CREATED: api-load-test (global) - 4 files, 180 lines
  MERGED:  batch-ops into nano-pdf - 2 sections added
  SKIPPED: data-transform (0.85 match with data-research)
 
Files created/modified:
  ~/.claude/skills/api-load-test/SKILL.md
  ~/.claude/skills/api-load-test/scripts/run-load-test.sh
  ~/.claude/skills/nano-pdf/SKILL.md (updated)
 
Validation: ALL PASS
Log: ~/.claude/skill-factory.log
 
Next steps:
  Test the new skill: /api-load-test
  Review: cat ~/.claude/skills/api-load-test/SKILL.md