tsaol/awesome-claude/git-commit
Claude Code and agent skill by tsaol/awesome-claude
- community
Checking that the SKILL.md file is still in the repository.
Review project consistency and commit changes. Checks code vs docs alignment, updates CHANGELOG/README/DESIGN.md, updates ~/history.log, bumps version, then commits, pushes, and deploys if configured. Use after finishing code modifications.
Install
npx vskill@latest install tsaol/awesome-claude/git-commitSKILL.md
Git Commit - Review, Fix, Commit & Deploy
Overview
This skill reviews project consistency after code changes to ensure:
- Code matches design documents
- CHANGELOG is updated for new features/fixes
- README reflects current functionality
- No outdated documentation
- ~/history.log is updated with session summary (if exists)
- Version number is bumped appropriately
- Deployment is triggered if configured in
~/.claude/collaboration.yml
When to Use
Trigger /git-commit after:
- Completing a feature implementation
- Fixing a bug
- Before creating a PR
- After significant code refactoring
Review Checklist
1. Code vs Design Docs
Check if implementation matches design:
- Architecture follows design patterns
- API endpoints match specification
- Data models align with schema
2. CHANGELOG Update
Verify CHANGELOG.md includes:
- New features added
- Bugs fixed
- Breaking changes noted
- Version number updated (if applicable)
3. README Accuracy
Ensure README.md reflects:
- Current installation steps
- Updated usage examples
- New CLI commands/options
- Correct configuration
4. History Log Update
Check if ~/history.log exists and update it with session summary:
If exists, append a summary of changes made in this session:
5. Version Bump
Automatically detect and bump the project version before committing.
5a. Detect version file:
5b. Determine bump type based on changes:
| Change Type | Bump | Examples | |
|---|---|---|---|
| Bug fix, typo, minor tweak | patch (0.0.x) | fix query bug, update docs typo | |
| New feature, enhancement | minor (0.x.0) | add user avatar upload, add new API endpoint | |
| Breaking change, major rewrite | major (x.0.0) | change API response format, remove deprecated endpoints |
Decision logic:
- Check git diff for breaking changes (removed public APIs, changed signatures, schema migrations)
- Check if new files/modules were added (likely minor)
- Default to patch if only modifications to existing files
5c. Bump the version:
5d. Update CHANGELOG with new version header:
If CHANGELOG.md exists, ensure the new version appears at the top:
Important:
- Always show the user the current version and proposed new version before bumping
- If no version file exists, skip this step and note it in the report
- Version bump changes are included in the same commit
6. Consistency Report
Generate a report:
Workflow
Auto Commit
After fixing all issues, automatically commit and push:
- Stage changes:
git addmodified files - Commit: Summarize code changes in simple, human-like message
- Push: Push to remote branch
- Create PR: If on feature branch, create PR with reviewer
Commit Message Style
ALWAYS use simple, human-like commit messages:
- Keep messages short and natural
- Summarize what the code changes actually do
- Use casual, everyday language
- Avoid formal conventions like "feat:", "chore:", "refactor:", etc.
- Write like a human developer would in daily work
- Never include any Claude-related attribution:
- No "Generated with Claude Code"
- No "Co-Authored-By: Claude"
Good examples:
add user loginfix slow queriesupdate packagesadd image download to browser fetcherstore s3 paths in opensearch
Bad examples:
feat: implement comprehensive user authentication system with JWT token validationchore: update dependencies to latest versionsdocs: update CHANGELOG for feature xyz
Auto Deploy
After a successful push, check if the project has deployment configured and trigger it.
Deploy Config
Deployment is configured per-project in ~/.claude/collaboration.yml:
Supported Deploy Methods
| Method | Description | Required Fields | |
|---|---|---|---|
ssm | AWS Systems Manager Run Command | instance, command | |
ssh | SSH to remote server | host, user, command | |
script | Run a local script | command |
Deploy Logic
Step 1: Check if deploy is configured
Identify current project by matching git remote -v against the repo field in collaboration.yml.
Step 2: Check if deploy should trigger
Deploy ONLY when:
- Current branch is
mainormaster(direct push workflow) - OR a PR was just merged to main (github-flow workflow)
- The push was successful
Do NOT deploy when:
- On a feature branch (not yet merged)
- Push failed
--no-deployflag is used
Step 3: Confirm with user
Always ask for confirmation before deploying. Never auto-deploy without user approval.
Step 4: Execute deployment
Step 5: Verify deployment
Step 6: Report deploy result
Usage
Example Output
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/git-commit/SKILL.md
Popularity
- Repository stars
- 62
- Repository forks
- 4
- 7-day trend score
- 21
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/tsaol/awesome-claude/git-commit)