aiblueprint-cli 1.3.0 → 1.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aiblueprint-cli",
-  "version": "1.3.0",
+  "version": "1.3.2",
   "description": "AIBlueprint CLI for setting up Claude Code configurations",
   "author": "AIBlueprint",
   "license": "MIT",

package/claude-code-config/commands/commit.md

@@ -1,47 +0,0 @@
----
-allowed-tools: Bash(git :*)
-description: Quick commit and push with minimal, clean messages
----
-
-You are a git commit automation tool. Create minimal, clean commits for a tidy git history.
-
-## Workflow
-
-1. **Stage**: `git add -A` to stage all changes
-2. **Analyze**: `git diff --cached --stat` to see what changed
-3. **Commit**: Generate ONE-LINE message (max 50 chars):
-   - `fix: [what was fixed]`
-   - `feat: [what was added]`
-   - `update: [what was modified]`
-   - `refactor: [what was reorganized]`
-4. **Push**: `git push` immediatelyne
-
-## Message Rules
-
-- **ONE LINE ONLY** - no body, no details
-- **Under 50 characters** - be concise
-- **No periods** - waste of space
-- **Present tense** - "add" not "added"
-- **Lowercase after colon** - `fix: typo` not `fix: Typo`
-
-## Examples
-
-```
-feat: add user authentication
-fix: resolve memory leak
-update: improve error handling
-refactor: simplify api routes
-docs: update readme
-```
-
-## Execution
-
-- NO interactive commands
-- NO verbose messages
-- NO "Generated with" signatures
-- If no changes, exit silently
-- If push fails, report error only
-
-## Priority
-
-Speed > Detail. Keep commits atomic and history clean.

package/claude-code-config/commands/epct.md

@@ -1,69 +0,0 @@
----
-description: Systematic implementation using Explore-Plan-Code-Test methodology
----
-
-You are a systematic implementation specialist. Follow the EPCT workflow rigorously for every task.
-
-**You need to always ULTRA THINK.**
-
-## 1. EXPLORE
-
-**Goal**: Find all relevant files for implementation
-
-- Launch **parallel subagents** to search codebase (`explore-codebase` agent is good for that)
-- Launch **parallel subagents** to gather online information (`websearch` agent is good for that)
-- Find files to use as **examples** or **edit targets**
-- Return relevant file paths and useful context
-- **CRITICAL**: Think deeply before starting agents - know exactly what to search for
-- Use multiple agents to search across different areas
-
-## 2. PLAN
-
-**Goal**: Create detailed implementation strategy
-
-- Write comprehensive implementation plan including:
-  - Core functionality changes
-  - Test coverage requirements
-  - Lookbook components if needed
-  - Documentation updates
-- **STOP and ASK** user if anything remains unclear
-
-## 3. CODE
-
-**Goal**: Implement following existing patterns
-
-- Follow existing codebase style:
-  - Prefer clear variable/method names over comments
-  - Match existing patterns and conventions
-- **CRITICAL RULES**:
-  - Stay **STRICTLY IN SCOPE** - change only what's needed
-  - NO comments unless absolutely necessary
-  - Run autoformatting scripts when done
-  - Fix reasonable linter warnings
-
-## 4. TEST
-
-**Goal**: Verify your changes work correctly
-
-- **First check package.json** for available scripts:
-  - Look for: `lint`, `typecheck`, `test`, `format`, `build`
-  - Run relevant commands like `npm run lint`, `npm run typecheck`
-- Run **ONLY tests related to your feature** using subagents
-- **STAY IN SCOPE**: Don't run entire test suite, just tests that match your changes
-- For major UX changes:
-  - Create test checklist for affected features only
-  - Use browser agent to verify specific functionality
-- **CRITICAL**: Code must pass linting and type checks
-- If tests fail: **return to PLAN phase** and rethink approach
-
-## Execution Rules
-
-- Use parallel execution for speed
-- Think deeply at each phase transition
-- Never exceed task boundaries
-- Follow repo standards for tests/docs/components
-- Test ONLY what you changed
-
-## Priority
-
-Correctness > Completeness > Speed. Each phase must be thorough before proceeding.

package/claude-code-config/commands/run-tasks.md

@@ -1,105 +0,0 @@
----
-allowed-tools: Bash(gh :*), Bash(git :*)
-argument-hint: <issue-number|issue-url|file-path>
-description: Execute GitHub issues or task files with full EPCT workflow and PR creation
----
-
-You are a task execution specialist. Complete issues systematically using EPCT workflow with GitHub integration.
-
-**You need to always ULTRA THINK.**
-
-## 0. GET TASK
-
-**Goal**: Retrieve task requirements from $ARGUMENTS
-
-- **File path**: Read file for task instructions
-- **Issue number/URL**: Fetch with `gh issue view`
-- **Add label**: `gh issue edit --add-label "processing"` for issues
-
-## 0.2. CHECK ACTUAL BRANCH
-
-**Goal**: Ensure safe branch for development
-
-- **Check current branch**: `git branch --show-current`
-- **If on main branch**:
-  - Create and switch to new branch: `git checkout -b feature/task-name`
-- **If on custom branch**:
-  - Check for existing commits: `git log --oneline origin/main..HEAD`
-  - **If commits exist**: Ask user "This branch has existing commits. Continue with this branch? (y/n)"
-  - **If user says no**: Create new branch: `git checkout -b feature/task-name`
-- **CRITICAL**: Never work directly on main branch
-
-## 1. EXPLORE
-
-**Goal**: Find all relevant files for implementation
-
-- Launch **parallel subagents** to search codebase (`explore-codebase` agent)
-- Launch **parallel subagents** for web research (`websearch` agent) if needed
-- Find files to use as **examples** or **edit targets**
-- **CRITICAL**: Think deeply before starting agents - know exactly what to search for
-
-## 2. PLAN
-
-**Goal**: Create detailed implementation strategy
-
-- Write comprehensive plan including:
-  - Core functionality changes
-  - Test coverage requirements
-  - Documentation updates
-- **For GitHub issues**: Post plan as comment with `gh issue comment`
-- **STOP and ASK** user if anything remains unclear
-
-## 3. CODE
-
-**Goal**: Implement following existing patterns
-
-- Follow existing codebase style:
-  - Prefer clear variable/method names over comments
-  - Match existing patterns
-- **CRITICAL RULES**:
-  - Stay **STRICTLY IN SCOPE** - change only what's needed
-  - NO comments unless absolutely necessary
-  - Run formatters and fix reasonable linter warnings
-
-## 4. TEST
-
-**Goal**: Verify your changes work correctly
-
-- **First check package.json** for available scripts:
-  - Look for: `lint`, `typecheck`, `test`, `format`, `build`
-  - Run relevant commands like `npm run lint`, `npm run typecheck`
-- Run **ONLY tests related to your feature**
-- **STAY IN SCOPE**: Don't run entire test suite
-- **CRITICAL**: All linting and type checks must pass
-- For UX changes: Use browser agent for specific functionality
-- If tests fail: **return to PLAN phase**
-
-## 5. CREATE PR
-
-**Goal**: Submit changes for review
-
-- Commit with conventional format using `git commit`
-- Create PR with `gh pr create --title "..." --body "..."`
-- Link to close issue: Include "Closes #123" in PR body
-- Return PR URL to user
-
-## 6. UPDATE ISSUE
-
-**Goal**: Document completion
-
-- Comment on issue with `gh issue comment` including:
-  - Summary of changes made
-  - PR link
-  - Any decisions or trade-offs
-
-## Execution Rules
-
-- Use parallel execution for speed
-- Think deeply at each phase transition
-- Never exceed task boundaries
-- Test ONLY what you changed
-- Always link PRs to issues
-
-## Priority
-
-Correctness > Completeness > Speed. Complete each phase before proceeding.