@m2015agg/git-skill 0.5.6 → 0.5.7

package/dist/templates/walkthrough.d.ts

@@ -1,5 +1,5 @@
 export declare const WALKTHROUGH = "# Git History Walkthrough\n\nUse git-skill to explore this repository's history.\n\n## Quick Start\n```\ngit-skill doctor          # Check setup health\ngit-skill hotspots        # Find churning files\ngit-skill trends          # View metric trends\ngit-skill search \"auth\"   # Search history\n```\n";
 export declare const PLAN_COMMAND = "---\ndescription: \"Plan a feature with git history awareness \u2014 checks what was tried before\"\n---\n\n# Planning Phase\n\nPlan implementation for the requested feature.\n\n**PROCESS:**\n\n1. **Gather Context**:\n   - `git-skill search \"<feature>\"` \u2014 check if this was attempted before\n   - `git-skill timeline <file>` \u2014 review history of files you plan to change\n   - `git-skill hotspots` \u2014 identify unstable files to approach carefully\n   - `git-skill coupling <file>` \u2014 what co-changes with target files\n\n2. **Check Git History**: Before designing changes, verify nothing was tried and reverted:\n   ```bash\n   git-skill search \"<feature keywords>\"\n   git-skill decisions --type revert\n   ```\n   If a similar approach was tried and reverted, note it in the plan and explain why this attempt is different.\n\n3. **Ask Questions**: Clarify requirements (max 5-7 questions)\n\n4. **Write Plan**: Create plan at `docs/plans/YYYY-MM-DD-[feature-name].md`\n\n**PLAN STRUCTURE:**\n```markdown\n# Feature Name\n\n## TLDR\n2-3 sentence summary\n\n## Context from Git History\n- Prior attempts: [what git-skill found]\n- Hotspot files: [files to be careful with]\n- Related decisions: [reverts, refactors that matter]\n\n## Requirements\n- Bullet points\n\n## Implementation Steps\n1. Step 1\n2. Step 2\n\n## Files to Modify/Create\n- `path/to/file` \u2014 description\n\n## Testing\n- How to verify this works\n```\n\n5. **Create GitHub Issue**: `gh issue create --title \"feat: ...\" --body \"See docs/plans/...\"`\n\n6. **STOP**: Wait for approval \u2014 DO NOT start implementation\n\n**CRITICAL:**\n- Check git history FIRST \u2014 don't re-try reverted approaches\n- Plans live in git (`docs/plans/`), not external tools\n- Be concise \u2014 the plan is for implementation, not documentation\n";
-export declare const IMPLEMENT_COMMAND = "---\ndescription: \"Implement a planned feature with TDD and frequent commits\"\n---\n\n# Implementation Phase\n\nImplement feature according to the plan file.\n\n**PROCESS:**\n\n1. **Read Plan**: Read the plan file carefully\n2. **Create Branch**:\n   ```bash\n   git checkout -b [feature-name]\n   git push -u origin [feature-name]\n   ```\n3. **Create Draft PR**:\n   ```bash\n   gh pr create --draft --title \"WIP: [Feature Name]\" --body \"See docs/plans/...\"\n   ```\n4. **Follow TDD** (Red \u2192 Green \u2192 Refactor):\n   - Write test that fails\n   - Implement minimal code to pass\n   - Refactor while keeping tests green\n\n5. **For Each Task**:\n   - Make changes following existing patterns in the codebase\n   - Run tests after each change\n   - Push commits frequently (backup points):\n     ```bash\n     git add . && git commit -m \"wip: [task]\" && git push\n     ```\n\n6. **STOP**: Notify completion \u2014 DO NOT finalize or merge\n\n**IMPORTANT:**\n- Follow plan exactly \u2014 don't deviate without asking\n- Push commits often (rollback points)\n- Keep user updated every 3-4 tasks\n- DO NOT finalize \u2014 just implement\n";
+export declare const IMPLEMENT_COMMAND = "---\ndescription: \"Implement a planned feature with TDD and frequent commits\"\n---\n\n# Implementation Phase\n\nImplement feature according to the plan file.\n\n**PROCESS:**\n\n1. **Read Plan**: Read the plan file carefully\n2. **Create Branch**:\n   ```bash\n   git checkout -b [feature-name]\n   git push -u origin [feature-name]\n   ```\n3. **Create Draft PR**:\n   ```bash\n   gh pr create --draft --title \"WIP: [Feature Name]\" --body \"See docs/plans/...\"\n   ```\n4. **Follow TDD** (Red \u2192 Green \u2192 Refactor):\n   - Write test that fails\n   - Implement minimal code to pass\n   - Refactor while keeping tests green\n\n5. **For Each Task**:\n   - Make changes following existing patterns in the codebase\n   - Run tests after each change\n   - Before committing, verify against history:\n     ```bash\n     git add .\n     git-skill verify\n     ```\n     If BLOCK: stop and discuss. If WARN: note it and proceed carefully.\n   - Push commits frequently (backup points):\n     ```bash\n     git commit -m \"wip: [task]\" && git push\n     ```\n\n6. **STOP**: Notify completion \u2014 DO NOT finalize or merge\n\n**IMPORTANT:**\n- Follow plan exactly \u2014 don't deviate without asking\n- Push commits often (rollback points)\n- Keep user updated every 3-4 tasks\n- DO NOT finalize \u2014 just implement\n";
 export declare const FINALIZE_COMMAND = "---\ndescription: \"Finalize a feature \u2014 tests, lint, commit, PR ready\"\n---\n\n# Finalization Phase\n\nFinalize the implemented feature.\n\n**PROCESS:**\n\n1. **Verify Tests Pass**:\n   ```bash\n   # Run your project's test suite\n   npm test        # Node.js\n   # pytest tests/  # Python\n   # cargo test     # Rust\n   ```\n   If tests fail, STOP and return to implementation.\n\n2. **Run git-skill verify**:\n   ```bash\n   git-skill verify\n   ```\n   Address any WARN or BLOCK findings before proceeding.\n\n3. **Update Documentation**: Add/update docs if needed\n\n4. **Create Final Commit**:\n   ```bash\n   git add .\n   git commit -m \"feat: [description]\n\n   Closes #[issue-number]\"\n   git push\n   ```\n\n5. **Convert PR to Ready**:\n   ```bash\n   gh pr ready\n   ```\n\n6. **Run Final Verification**:\n   ```bash\n   git-skill doctor\n   git-skill hotspots --limit 3\n   ```\n   Show output \u2014 never claim completion without proof.\n\n7. **STOP**: Report completion with PR link and verification output\n\n**CHECKLIST:**\n- [ ] All tests passing\n- [ ] `git-skill verify` \u2014 no BLOCK findings\n- [ ] Documentation updated\n- [ ] Commit message follows conventions\n- [ ] PR converted to ready\n- [ ] Verification output shown\n\n**IMPORTANT:**\n- NEVER skip verification\n- NEVER merge PR \u2014 user reviews and merges\n- If anything fails, return to implementation\n";
-export declare const REVIEW_COMMAND = "---\ndescription: \"Code review with git history verification \u2014 checks for repeated mistakes before merge\"\n---\n\n# Code Review with History Verification\n\nReview the current branch changes before merging.\n\n**PROCESS:**\n\n1. **Run tests**:\n   ```bash\n   # Run the project's test suite (adjust command for your project)\n   npm test        # Node.js\n   # pytest         # Python\n   # cargo test     # Rust\n   ```\n\n2. **Git History Verification** (prevent re-trying failed approaches):\n   ```bash\n   git-skill verify\n   ```\n   If `git-skill verify` returns WARN or BLOCK:\n   - **BLOCK**: STOP. This change re-introduces something that was explicitly reverted. Ask the user before proceeding.\n   - **WARN**: Note the warning. Check if the current approach addresses the previous failure. Proceed with caution.\n   - **PASS**: No concerns from history.\n\n3. **Check codebase health**:\n   ```bash\n   git-skill doctor\n   git-skill hotspots --limit 5\n   ```\n   Flag any files being modified that appear in the hotspots list.\n\n4. **Review against criteria**:\n   - **Critical** (must fix): Security vulnerabilities, data loss risks, breaking changes, tests failing\n   - **Major** (should fix): Missing error handling, pattern violations, missing tests\n   - **Minor** (optional): Style, docs, optimization\n\n5. **Auto-fix critical/major issues**:\n   - Fix issues following established patterns\n   - Run tests after each fix\n   - Commit fixes separately\n\n6. **Report findings**:\n   - List issues found and fixed\n   - List any WARN/BLOCK from git-skill verify\n   - Provide verification commands\n   - Recommend proceeding or returning to implementation\n\n**IMPORTANT:**\n- `git-skill verify` is authoritative \u2014 if it says something was reverted before, take it seriously\n- Auto-fix critical/major issues, don't just report them\n- Always run tests after fixes\n";
+export declare const REVIEW_COMMAND = "---\ndescription: \"Code review with git history verification \u2014 checks for repeated mistakes before merge\"\n---\n\n# Code Review with History Verification\n\nReview the current branch changes before merging.\n\n**PROCESS:**\n\n1. **Run tests**:\n   ```bash\n   # Run the project's test suite (adjust command for your project)\n   npm test        # Node.js\n   # pytest         # Python\n   # cargo test     # Rust\n   ```\n\n2. **Git History Verification** (prevent re-trying failed approaches):\n   ```bash\n   git-skill verify\n   ```\n   If `git-skill verify` returns WARN or BLOCK:\n   - **BLOCK**: STOP. This change re-introduces something that was explicitly reverted. Ask the user before proceeding.\n   - **WARN**: Note the warning. Check if the current approach addresses the previous failure. Proceed with caution.\n   - **PASS**: No concerns from history.\n\n3. **Review scope and codebase health**:\n   ```bash\n   git-skill diff-summary HEAD~5..HEAD    # summarize what changed in this branch\n   git-skill hotspots --limit 5           # flag churning files\n   ```\n   Flag any files being modified that appear in the hotspots list.\n\n4. **Review against criteria**:\n   - **Critical** (must fix): Security vulnerabilities, data loss risks, breaking changes, tests failing\n   - **Major** (should fix): Missing error handling, pattern violations, missing tests\n   - **Minor** (optional): Style, docs, optimization\n\n5. **Auto-fix critical/major issues**:\n   - Fix issues following established patterns\n   - Run tests after each fix\n   - Commit fixes separately\n\n6. **Report findings**:\n   - List issues found and fixed\n   - List any WARN/BLOCK from git-skill verify\n   - Provide verification commands\n   - Recommend proceeding or returning to implementation\n\n**IMPORTANT:**\n- `git-skill verify` is authoritative \u2014 if it says something was reverted before, take it seriously\n- Auto-fix critical/major issues, don't just report them\n- Always run tests after fixes\n";

package/dist/templates/walkthrough.js

@@ -100,9 +100,15 @@ Implement feature according to the plan file.
 5. **For Each Task**:
    - Make changes following existing patterns in the codebase
    - Run tests after each change
+   - Before committing, verify against history:
+     \`\`\`bash
+     git add .
+     git-skill verify
+     \`\`\`
+     If BLOCK: stop and discuss. If WARN: note it and proceed carefully.
    - Push commits frequently (backup points):
      \`\`\`bash
-     git add . && git commit -m "wip: [task]" && git push
+     git commit -m "wip: [task]" && git push
      \`\`\`
 
 6. **STOP**: Notify completion — DO NOT finalize or merge
@@ -203,10 +209,10 @@ Review the current branch changes before merging.
    - **WARN**: Note the warning. Check if the current approach addresses the previous failure. Proceed with caution.
    - **PASS**: No concerns from history.
 
-3. **Check codebase health**:
+3. **Review scope and codebase health**:
    \`\`\`bash
-   git-skill doctor
-   git-skill hotspots --limit 5
+   git-skill diff-summary HEAD~5..HEAD    # summarize what changed in this branch
+   git-skill hotspots --limit 5           # flag churning files
    \`\`\`
    Flag any files being modified that appear in the hotspots list.
 

package/dist/templates/walkthrough.js.map

@@ -1 +1 @@
-{"version":3,"file":"walkthrough.js","sourceRoot":"","sources":["../../src/templates/walkthrough.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;CAW1B,CAAC;AAEF,MAAM,CAAC,MAAM,YAAY,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6D3B,CAAC;AAEF,MAAM,CAAC,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwChC,CAAC;AAEF,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8D/B,CAAC;AAEF,MAAM,CAAC,MAAM,cAAc,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsD7B,CAAC"}
+{"version":3,"file":"walkthrough.js","sourceRoot":"","sources":["../../src/templates/walkthrough.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;CAW1B,CAAC;AAEF,MAAM,CAAC,MAAM,YAAY,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6D3B,CAAC;AAEF,MAAM,CAAC,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8ChC,CAAC;AAEF,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8D/B,CAAC;AAEF,MAAM,CAAC,MAAM,cAAc,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsD7B,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m2015agg/git-skill",
-  "version": "0.5.6",
+  "version": "0.5.7",
   "description": "Git history intelligence for LLMs — institutional memory over codebase evolution",
   "type": "module",
   "main": "./dist/index.js",