@m2015agg/git-skill 0.5.7 → 0.5.8

package/dist/templates/walkthrough.d.ts

@@ -1,4 +1,4 @@
-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 WALKTHROUGH = "---\ndescription: Interactive walkthrough of git history \u2014 hotspots, decisions, expertise, health trends via git-skill CLI\nallowed-tools: Read, Bash(git-skill:*)\n---\n\n# /git-history \u2014 Codebase History Walkthrough\n\nWhen the user invokes this command, guide them through their codebase history interactively.\n\n## Steps\n\n1. **Check setup health**\n   Run: `git-skill doctor`\n   Confirm the database is fresh and hook is installed. Note commit count and snapshot age.\n\n2. **Show what's churning**\n   Run: `git-skill hotspots --limit 10`\n   Explain which files have the most churn. Flag any that are suspicious (high edit count in a short period = instability).\n\n3. **Show recent decisions**\n   Run: `git-skill decisions --limit 10`\n   Walk through the major decision points \u2014 reverts, big refactors, architecture changes. Explain the impact of each.\n\n4. **Health trends**\n   Run: `git-skill trends`\n   Summarize the metric trends: is revert rate going up or down? Is scope creep improving? Are commits getting smaller or larger?\n\n5. **Explore a specific area**\n   Ask the user which file or directory they want to investigate, or pick the top hotspot.\n   Run: `git-skill timeline <path>`\n   Show the full evolution \u2014 every commit, who made it, what changed.\n\n6. **Who knows what**\n   Run: `git-skill experts <path>` (using the path from step 5)\n   Show who has the most context on that area of the codebase.\n\n7. **Check for co-change patterns**\n   Run: `git-skill coupling <path>`\n   Reveal files that always change together \u2014 hidden dependencies the team should know about.\n\n8. **Open Q&A**\n   Say: \"Ask me anything about your codebase history \u2014 I can search commits, trace file evolution, find decision points, or check what was tried before.\"\n\n## Tips\n- Use `git-skill search \"<query>\"` for free-text search across all commits and file paths\n- Use `git-skill why <hash>` to understand the intent behind any commit (requires enrichment)\n- Use `git-skill verify` before committing to check if staged changes repeat past mistakes\n- Use `git-skill diff-summary v1.0..v1.1` for a release-level summary between two refs\n- Use `git-skill regression` to detect change-point shifts in metrics\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   - 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";

package/dist/templates/walkthrough.js

@@ -1,14 +1,52 @@
-export const WALKTHROUGH = `# Git History Walkthrough
+export const WALKTHROUGH = `---
+description: Interactive walkthrough of git history — hotspots, decisions, expertise, health trends via git-skill CLI
+allowed-tools: Read, Bash(git-skill:*)
+---
 
-Use git-skill to explore this repository's history.
+# /git-history — Codebase History Walkthrough
 
-## Quick Start
-\`\`\`
-git-skill doctor          # Check setup health
-git-skill hotspots        # Find churning files
-git-skill trends          # View metric trends
-git-skill search "auth"   # Search history
-\`\`\`
+When the user invokes this command, guide them through their codebase history interactively.
+
+## Steps
+
+1. **Check setup health**
+   Run: \`git-skill doctor\`
+   Confirm the database is fresh and hook is installed. Note commit count and snapshot age.
+
+2. **Show what's churning**
+   Run: \`git-skill hotspots --limit 10\`
+   Explain which files have the most churn. Flag any that are suspicious (high edit count in a short period = instability).
+
+3. **Show recent decisions**
+   Run: \`git-skill decisions --limit 10\`
+   Walk through the major decision points — reverts, big refactors, architecture changes. Explain the impact of each.
+
+4. **Health trends**
+   Run: \`git-skill trends\`
+   Summarize the metric trends: is revert rate going up or down? Is scope creep improving? Are commits getting smaller or larger?
+
+5. **Explore a specific area**
+   Ask the user which file or directory they want to investigate, or pick the top hotspot.
+   Run: \`git-skill timeline <path>\`
+   Show the full evolution — every commit, who made it, what changed.
+
+6. **Who knows what**
+   Run: \`git-skill experts <path>\` (using the path from step 5)
+   Show who has the most context on that area of the codebase.
+
+7. **Check for co-change patterns**
+   Run: \`git-skill coupling <path>\`
+   Reveal files that always change together — hidden dependencies the team should know about.
+
+8. **Open Q&A**
+   Say: "Ask me anything about your codebase history — I can search commits, trace file evolution, find decision points, or check what was tried before."
+
+## Tips
+- Use \`git-skill search "<query>"\` for free-text search across all commits and file paths
+- Use \`git-skill why <hash>\` to understand the intent behind any commit (requires enrichment)
+- Use \`git-skill verify\` before committing to check if staged changes repeat past mistakes
+- Use \`git-skill diff-summary v1.0..v1.1\` for a release-level summary between two refs
+- Use \`git-skill regression\` to detect change-point shifts in metrics
 `;
 export const PLAN_COMMAND = `---
 description: "Plan a feature with git history awareness — checks what was tried before"

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;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8ChC,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;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiD1B,CAAC;AAGF,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.7",
+  "version": "0.5.8",
   "description": "Git history intelligence for LLMs — institutional memory over codebase evolution",
   "type": "module",
   "main": "./dist/index.js",