5-phase-workflow 1.3.0 → 1.4.1

package/bin/install.js

@@ -373,7 +373,11 @@ function getDefaultConfig(projectType) {
       command: 'auto',
       testCommand: 'auto'
     },
-    reviewTool: 'claude'
+    reviewTool: 'claude',
+    git: {
+      autoCommit: false,
+      commitMessage: { pattern: '{ticket-id} {short-description}' }
+    }
   };
 
   // Project-specific overrides

package/package.json

@@ -1,12 +1,15 @@
 {
   "name": "5-phase-workflow",
-  "version": "1.3.0",
+  "version": "1.4.1",
   "description": "A 5-phase feature development workflow for Claude Code",
   "bin": {
     "5-phase-workflow": "bin/install.js"
   },
   "scripts": {
-    "test": "bash test/verify-install-js.sh",
+    "test": "bash test/verify-install-js.sh && bash test/test-check-updates-hook.sh && bash test/test-update-system.sh",
+    "test:install": "bash test/verify-install-js.sh",
+    "test:hook": "bash test/test-check-updates-hook.sh",
+    "test:update": "bash test/test-update-system.sh",
     "verify": "bash test/verify-install-js.sh"
   },
   "files": [

package/src/commands/5/configure.md

@@ -145,6 +145,9 @@ if command -v coderabbit &> /dev/null; then
 fi
 
 # IDE MCP (JetBrains) - check if MCP tools are available
+
+# Context7 - up-to-date documentation MCP server
+# Check if context7 tools are available (resolve-library-id, query-docs)
 ```
 
 **1e. Check CLAUDE.md:**
@@ -326,7 +329,21 @@ If "Cancel": Exit immediately with message "Configuration unchanged."
 - "Suggested test command: `{command}`. Use this?"
   - Options: "Yes (recommended)", "Customize", "None (no test step)"
 
-**2f. Review tool preference:**
+**2f. Auto-commit during implementation:**
+- "Should Claude make atomic commits during implementation? This creates a commit after each step, enabling progress tracking and easy rollback."
+  - Options:
+    1. "No (recommended)" → `git.autoCommit: false`
+    2. "Yes - commit after each implementation step" → `git.autoCommit: true`
+
+**2g. Commit message pattern (only if auto-commit = Yes):**
+- "What commit message format would you like?"
+  - Options:
+    1. "Default: `{ticket-id} {short-description}` (Recommended)"
+    2. "Conventional: `feat({ticket-id}): {short-description}`"
+    3. "Custom pattern" → free text
+- Note: "Body will automatically include bullet points of changes."
+
+**2h. Review tool preference:**
 - "Which code review tool would you like to use?"
   - Options:
     1. "Claude (built-in, no setup needed)" — always available
@@ -339,11 +356,24 @@ If "Cancel": Exit immediately with message "Configuration unchanged."
     - Then: `coderabbit auth login`
   - Record the preference as `coderabbit` regardless (will prompt at review time if still missing)
 
-**2g. Confirm CLAUDE.md generation:**
+**2i. Context7 documentation plugin:**
+
+Context7 provides up-to-date, version-specific documentation and code examples directly in your prompts. It solves a common problem with LLMs: outdated training data leading to hallucinated APIs and deprecated code patterns.
+
+- If Context7 was detected in Step 1d (resolve-library-id and query-docs tools available):
+  - "Context7 is already installed. ✓"
+- If Context7 was NOT detected:
+  - "Would you like to install Context7? It provides up-to-date, version-specific documentation directly in prompts — helping avoid hallucinated APIs and deprecated patterns."
+  - Options:
+    1. "Install now (recommended)" — run `claude mcp add context7 -- npx -y @anthropic-ai/claude-code-mcp-server-context7` via Bash
+    2. "Skip"
+  - If user selects "Install now": execute the install command
+
+**2j. Confirm CLAUDE.md generation:**
 - "Generate/update CLAUDE.md? This will analyze your codebase to document structure and conventions."
   - Options: "Yes (recommended)", "Skip"
 
-**2h. Review detected patterns for skill generation:**
+**2k. Review detected patterns for skill generation:**
 
 Present ONLY patterns that were actually detected in steps 1g and 1h.
 
@@ -408,7 +438,10 @@ Create `.claude/.5/config.json` with the following values:
 - Test timeout: 300000ms
 - CodeRabbit: {available/not-available}, authenticated: {yes/no}
 - IDE integration: {available/not-available}, type: {type}
+- Context7: {available/not-available}
 - Review tool: {claude/coderabbit/none}
+- Auto-commit: {yes/no}
+- Commit message pattern: {pattern or "default"}
 
 ### Requirement 2: Generate Documentation Files
 Analyze the codebase and generate modular documentation:
@@ -555,6 +588,12 @@ User: "Yes"
 Claude: "Test command: `npm test`. Use this?"
 User: "Yes"
 
+Claude: "Should Claude make atomic commits during implementation?"
+User: "No"
+
+Claude: "Which code review tool would you like to use?"
+User: "Claude (built-in)"
+
 Claude: "Generate CLAUDE.md with codebase analysis?"
 User: "Yes"
 

package/src/commands/5/implement-feature.md

@@ -1,7 +1,7 @@
 ---
 name: 5:implement-feature
 description: Executes an implementation plan by delegating to agents. Phase 3 of the 5-phase workflow.
-allowed-tools: Task, Read, Write, Glob, Grep
+allowed-tools: Task, Read, Write, Glob, Grep, Bash
 context: fork
 user-invocable: true
 ---
@@ -10,7 +10,11 @@ user-invocable: true
 
 ## Prerequisites Check
 
-**CRITICAL: Check for configuration before proceeding**
+**CRITICAL: Check for configuration before proceeding (skip for CONFIGURE feature)**
+
+If the feature argument is `CONFIGURE`, skip this check entirely — the CONFIGURE workflow is what creates the config file.
+
+For all other features, run this check:
 
 ```bash
 if [ ! -f ".claude/.5/config.json" ]; then
@@ -27,7 +31,7 @@ if [ ! -f ".claude/.5/config.json" ]; then
 fi
 ```
 
-**If config doesn't exist, STOP IMMEDIATELY. Do not proceed with the workflow.**
+**If config doesn't exist and the feature is NOT `CONFIGURE`, STOP IMMEDIATELY. Do not proceed with the workflow.**
 
 Execute an implementation plan by delegating work to agents.
 
@@ -46,7 +50,7 @@ Do NOT write code directly. Spawn agents to do the work.
 
 ## Process
 
-### Step 1: Load Plan
+### Step 1: Load Plan and Config
 
 Read `.5/features/{feature-name}/plan.md` (where `{feature-name}` is the argument provided).
 
@@ -58,6 +62,10 @@ Parse:
 
 If the plan doesn't exist, tell the user to run `/5:plan-implementation` first.
 
+Also read `.claude/.5/config.json` and extract:
+- `git.autoCommit` (boolean, default `false`)
+- `git.commitMessage.pattern` (string, default `{ticket-id} {short-description}`)
+
 ### Step 2: Initialize State
 
 Create `.5/features/{feature-name}/state.json`:
@@ -180,7 +188,39 @@ Update state.json:
 }
 ```
 
-**3e. Handle failures**
+**3e. Auto-Commit Step (if enabled)**
+
+Only fires if `git.autoCommit: true` AND at least one component in the step succeeded.
+
+1. Stage **only** the specific files from the plan's components table for this step (never `git add .`)
+2. Commit using the configured `git.commitMessage.pattern`:
+   - `{ticket-id}` → ticket ID from plan frontmatter
+   - `{short-description}` → auto-generated summary of the step (imperative mood, max 50 chars for the full first line)
+   - Body: one bullet per completed component
+
+```bash
+# Stage only specific files from this step's components
+git add {file-1} {file-2} ...
+
+# Commit with configured pattern + body
+git commit -m "{ticket-id} {short-description}
+
+- {concise change 1}
+- {concise change 2}"
+```
+
+3. If commit fails → log warning, record in `state.json` under `commitResults` array, continue
+4. If all components in the step failed → skip commit entirely
+
+**Example commit:**
+```
+PROJ-1234 add schedule model and types
+
+- Create Schedule.ts entity model
+- Create schedule.ts type definitions
+```
+
+**3f. Handle failures**
 
 If any component failed:
 - Log the failure in state.json
@@ -223,6 +263,7 @@ Implementation complete!
 - {N} components created/modified
 - Build: {status}
 - Tests: {status}
+{If git.autoCommit was true: "- Commits: {N} atomic commits created"}
 
 {If any failures: list them}
 

package/src/commands/5/plan-implementation.md

@@ -10,7 +10,11 @@ user-invocable: true
 
 ## Prerequisites Check
 
-**CRITICAL: Check for configuration before proceeding**
+**CRITICAL: Check for configuration before proceeding (skip for CONFIGURE feature)**
+
+If the feature argument is `CONFIGURE`, skip this check entirely — the CONFIGURE workflow is what creates the config file.
+
+For all other features, run this check:
 
 ```bash
 if [ ! -f ".claude/.5/config.json" ]; then
@@ -27,7 +31,7 @@ if [ ! -f ".claude/.5/config.json" ]; then
 fi
 ```
 
-**If config doesn't exist, STOP IMMEDIATELY. Do not proceed with the workflow.**
+**If config doesn't exist and the feature is NOT `CONFIGURE`, STOP IMMEDIATELY. Do not proceed with the workflow.**
 
 Create an implementation plan that maps a feature spec to concrete components.
 

package/src/commands/5/quick-implement.md

@@ -51,7 +51,7 @@ Your job is NOT:
 ❌ Skip clarifying questions if unclear
 ❌ Skip state file updates
 ❌ Create feature spec files (use full workflow)
-❌ Commit changes (user handles this)
+❌ Commit without config - Only commit if git.autoCommit is enabled
 
 **This is a FAST PATH for well-understood, small tasks. For anything complex, use the full workflow.**
 
@@ -63,7 +63,7 @@ Your job is NOT:
 - ❌ **Skip clarifying questions** - If implementation is unclear, ask first
 - ❌ **Skip state updates** - State file updates are MANDATORY
 - ❌ **Create feature specs** - This is for quick tasks, not full features
-- ❌ **Auto-commit** - User handles commits
+- ❌ **Commit without config** - Only commit if git.autoCommit is enabled
 - ❌ **Skip plan approval** - Always show plan and get user approval first
 
 **If the task involves more than 5 files or multiple domains, STOP and recommend the full workflow instead.**
@@ -79,7 +79,7 @@ Use AskUserQuestion:
 
 Store as `$DESCRIPTION`.
 
-### Step 2: Extract Ticket ID
+### Step 2: Extract Ticket ID and Load Config
 
 ```bash
 git branch --show-current
@@ -87,6 +87,10 @@ git branch --show-current
 
 Extract ticket ID using configurable pattern from config (e.g., `PROJ-\d+` or `\d+`). If not found, ask developer.
 
+Also read `.claude/.5/config.json` and extract:
+- `git.autoCommit` (boolean, default `false`)
+- `git.commitMessage.pattern` (string, default `{ticket-id} {short-description}`)
+
 ### Step 3: Generate Identifiers
 
 ```bash
@@ -268,6 +272,32 @@ Skill tool call:
   args: "{affected test modules}"
 ```
 
+### Step 9b: Auto-Commit (if enabled)
+
+Only fires if `git.autoCommit: true` AND build passed in Step 9.
+
+Creates a **single commit** for all components (not per-component — quick-implement is for small tasks):
+
+1. Stage **only** the specific files from the plan's components (never `git add .`)
+2. Commit using the configured `git.commitMessage.pattern`:
+   - `{ticket-id}` → ticket ID
+   - `{short-description}` → auto-generated summary (imperative mood, max 50 chars for full first line)
+   - Body: one bullet per component
+
+```bash
+# Stage only specific files
+git add {file-1} {file-2} ...
+
+# Commit with configured pattern + body
+git commit -m "{ticket-id} {short-description}
+
+- {concise change 1}
+- {concise change 2}"
+```
+
+3. If commit fails → log warning, record in `state.json`, continue
+4. If build failed in Step 9 → skip commit entirely
+
 ### Step 10: Update State and Report (MANDATORY)
 
 **CRITICAL**: You MUST update the state file to mark completion.
@@ -303,10 +333,14 @@ Components created/modified:
 
 Build: Success
 Tests: {Success | Skipped}
+{If git.autoCommit was true: "Commit: {Success | Failed | Skipped (build failed)}"}
 
 State: .5/features/${feature_name}/state.json
 
 Next steps:
+{If auto-commit fired successfully:}
+1. For a new task, run `/clear` before starting
+{If auto-commit not enabled or commit skipped:}
 1. Review and commit changes
 2. For a new task, run `/clear` before starting
 ```

package/src/commands/5/review-code.md

@@ -11,7 +11,11 @@ user-invocable: true
 
 ## Prerequisites Check
 
-**CRITICAL: Check for configuration before proceeding**
+**CRITICAL: Check for configuration before proceeding (skip for CONFIGURE feature)**
+
+If the feature argument is `CONFIGURE`, skip this check entirely — the CONFIGURE workflow is what creates the config file.
+
+For all other features, run this check:
 
 ```bash
 if [ ! -f ".claude/.5/config.json" ]; then
@@ -28,7 +32,7 @@ if [ ! -f ".claude/.5/config.json" ]; then
 fi
 ```
 
-**If config doesn't exist, STOP IMMEDIATELY. Do not proceed with the workflow.**
+**If config doesn't exist and the feature is NOT `CONFIGURE`, STOP IMMEDIATELY. Do not proceed with the workflow.**
 
 ## Overview
 

package/src/commands/5/verify-implementation.md

@@ -10,7 +10,11 @@ user-invocable: true
 
 ## Prerequisites Check
 
-**CRITICAL: Check for configuration before proceeding**
+**CRITICAL: Check for configuration before proceeding (skip for CONFIGURE feature)**
+
+If the feature argument is `CONFIGURE`, skip this check entirely — the CONFIGURE workflow is what creates the config file.
+
+For all other features, run this check:
 
 ```bash
 if [ ! -f ".claude/.5/config.json" ]; then
@@ -27,7 +31,7 @@ if [ ! -f ".claude/.5/config.json" ]; then
 fi
 ```
 
-**If config doesn't exist, STOP IMMEDIATELY. Do not proceed with the workflow.**
+**If config doesn't exist and the feature is NOT `CONFIGURE`, STOP IMMEDIATELY. Do not proceed with the workflow.**
 
 Verify that an implementation is complete, correct, and meets feature requirements through multi-layer verification.
 
@@ -70,11 +74,16 @@ Note: feature.md not found — skipping feature completeness checks.
 This is normal for quick-implement workflows. Infrastructure and quality checks will still run.
 ```
 
+Also read `.claude/.5/config.json` and extract:
+- `git.autoCommit` (boolean, default `false`)
+- `git.commitMessage.pattern` (string, default `{ticket-id} {short-description}`)
+
 Extract from artifacts:
 - Components table from `plan.md` (step, component, action, file, description, complexity)
 - Build and test commands from `plan.md`
 - Completed/failed components from `state.json`
 - Acceptance criteria and functional requirements from `feature.md` (if present)
+- Number of commits created from `state.json` `commitResults` (if auto-commit was used)
 
 ### Step 2: Infrastructure Verification (Layer 1)
 
@@ -255,7 +264,11 @@ Layer 2 (Feature Completeness): {N}/{N} criteria satisfied, {N}/{N} requirements
 Layer 3 (Quality): {N}/{N} new files have tests
 
 Report: .5/{feature-name}/verification.md
+```
+
+**If `git.autoCommit: false` (default):** offer to commit.
 
+```
 Would you like to commit these changes?
 ```
 
@@ -265,6 +278,12 @@ Use AskUserQuestion with options:
 
 If yes: stage and commit with message format `{TICKET-ID} {description}`.
 
+**If `git.autoCommit: true`:** skip the commit offer.
+
+```
+Changes were already committed during implementation ({N} atomic commits).
+```
+
 Then go to Step 11 (Next Steps).
 
 **If PARTIAL or FAILED:**
@@ -359,6 +378,22 @@ After all fixes are applied, re-run build and tests:
 {test-command}
 ```
 
+**If `git.autoCommit: true` and fixes succeeded (build + tests pass):**
+
+Auto-commit the fix files:
+```bash
+# Stage only the specific fix files
+git add {fix-file-1} {fix-file-2} ...
+
+# Commit with ticket ID
+git commit -m "{ticket-id} fix verification issues
+
+- {concise fix 1}
+- {concise fix 2}"
+```
+
+If commit fails → log warning, continue.
+
 Update `fix-plan.md` with results:
 - Mark each fix as APPLIED / FAILED
 - Record build and test results after fixes
@@ -369,6 +404,7 @@ Applied {N} fixes.
 
 Build: {status}
 Tests: {status}
+{If git.autoCommit was true: "Commit: {Success | Failed | Skipped}"}
 
 {If any fixes failed, list them}
 

package/src/hooks/check-updates.js

@@ -3,19 +3,19 @@
 const fs = require('fs');
 const path = require('path');
 
-// Read stdin (Claude Code passes JSON)
-let inputData = '';
-process.stdin.on('data', (chunk) => {
-  inputData += chunk;
-});
-
-process.stdin.on('end', async () => {
+// Read JSON from stdin
+let input = '';
+process.stdin.setEncoding('utf8');
+process.stdin.on('data', chunk => input += chunk);
+process.stdin.on('end', () => {
   try {
-    // Parse hook input (contains workspace info)
-    const hookData = JSON.parse(inputData);
-    const workspaceDir = hookData.workingDirectory || process.cwd();
+    let workspaceDir = process.cwd();
+    if (input.trim()) {
+      const data = JSON.parse(input);
+      workspaceDir = data.cwd || data.workspace?.current_dir || workspaceDir;
+    }
 
-    await checkForUpdates(workspaceDir);
+    checkForUpdates(workspaceDir).catch(() => process.exit(0));
   } catch (e) {
     // Silent failure - don't block on errors
     process.exit(0);

package/src/settings.json

@@ -6,10 +6,12 @@
   "hooks": {
     "SessionStart": [
       {
+        "matcher": "startup",
         "hooks": [
           {
             "type": "command",
-            "command": "node .claude/hooks/check-updates.js"
+            "command": "node .claude/hooks/check-updates.js",
+            "timeout": 10
           }
         ]
       }

package/src/skills/configure-project/SKILL.md

@@ -55,14 +55,23 @@ It handles three distinct tasks, invoked with different parameters per component
     "ide": {
       "available": false,
       "type": null
+    },
+    "context7": {
+      "available": false
     }
   },
-  "reviewTool": "claude" or "coderabbit" or "none"
+  "reviewTool": "claude" or "coderabbit" or "none",
+  "git": {
+    "autoCommit": false,
+    "commitMessage": {
+      "pattern": "{ticket-id} {short-description}"
+    }
+  }
 }
 ```
 
 **Process:**
-1. Read all values from the feature spec (`.5/features/CONFIGURE/feature.md`)
+1. Read all values from the feature spec (`.5/features/CONFIGURE/feature.md`), including `git.autoCommit` and `git.commitMessage.pattern`
 2. Ensure `.claude/.5/` directory exists (create with `mkdir -p` if needed)
 3. Write `config.json` with pretty-printed JSON
 4. Read back to verify correctness