blueprint-derive-ruleslisted

# /blueprint:derive-rules Extract project decisions from git commit history and codify them as Claude rules. Newer commits override older decisions when conflicts exist. **Use case**: Derive implicit project patterns from git history to establish consistent AI-assisted development guidelines. **Usage**: `/blueprint:derive-rules [--since DATE] [--scope SCOPE]` ## When to Use This Skill | Use this skill when... | Use alternative when... | |------------------------|-------------------------| | Want to extract implicit decisions from git history | Creating rules from requirements (use PRDs instead) | | Project has significant commit history | New project with little history | | Establishing project coding standards | Quick manual rule creation | ## Context - Git repository: !`git rev-parse --git-dir` - Blueprint initialized: !`find docs/blueprint -maxdepth 1 -name 'manifest.json' -type f` - Total commits: !`git rev-list --count HEAD` - Conventional commits %: !`git log --format="%s"` - Existing rules in default location: !`find .claude/rules -maxdepth 1 -name "*.md" -type f` - Existing rules in blueprint subdir: !`find .claude/rules/blueprint -maxdepth 1 -name "*.md" -type f` ## Parameters Parse `$ARGUMENTS`: - `--since DATE`: Analyze commits from specific date (e.g., `--since 2024-01-01`) - `--scope SCOPE`: Focus on specific area (e.g., `--scope api`, `--scope testing`) ## Execution Execute the complete git-to-rules derivation workflow: ### Step 0: Resolve the outpu