commit
starsforks
How to install commit?
parcadei/continuous-claude-v3/commit
$npx -y skills add parcadei/Continuous-Claude-v3 --skill commitCreate git commits with user approval and no Claude attribution
SKILL.md
| 1 | # Commit Changes |
| 2 | |
| 3 | You are tasked with creating git commits for the changes made during this session. |
| 4 | |
| 5 | ## Process: |
| 6 | |
| 7 | 1. **Think about what changed:** |
| 8 | - Review the conversation history and understand what was accomplished |
| 9 | - Run `git status` to see current changes |
| 10 | - Run `git diff` to understand the modifications |
| 11 | - Consider whether changes should be one commit or multiple logical commits |
| 12 | |
| 13 | 2. **Plan your commit(s):** |
| 14 | - Identify which files belong together |
| 15 | - Draft clear, descriptive commit messages |
| 16 | - Use imperative mood in commit messages |
| 17 | - Focus on why the changes were made, not just what |
| 18 | |
| 19 | 3. **Present your plan to the user:** |
| 20 | - List the files you plan to add for each commit |
| 21 | - Show the commit message(s) you'll use |
| 22 | - Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?" |
| 23 | |
| 24 | 4. **Execute upon confirmation:** |
| 25 | - Use `git add` with specific files (never use `-A` or `.`) |
| 26 | - Create commits with your planned messages |
| 27 | - Show the result with `git log --oneline -n [number]` |
| 28 | |
| 29 | 5. **Generate reasoning (after each commit):** |
| 30 | - Run: `bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <commit-hash> "<commit-message>"` |
| 31 | - This captures what was tried during development (build failures, fixes) |
| 32 | - The reasoning file helps future sessions understand past decisions |
| 33 | - Stored in `.git/claude/commits/<hash>/reasoning.md` |
| 34 | |
| 35 | ## Important: |
| 36 | - **NEVER add co-author information or Claude attribution** |
| 37 | - Commits should be authored solely by the user |
| 38 | - Do not include any "Generated with Claude" messages |
| 39 | - Do not add "Co-Authored-By" lines |
| 40 | - Write commit messages as if the user wrote them |
| 41 | |
| 42 | ## Remember: |
| 43 | - You have the full context of what was done in this session |
| 44 | - Group related changes together |
| 45 | - Keep commits focused and atomic when possible |
| 46 | - The user trusts your judgment - they asked you to commit |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
