Assists in crafting atomic, well-structured git commits following professional best practices.
Install
mkdir -p .claude/skills/git-commits && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/193" && unzip -o skill.zip -d .claude/skills/git-commits && rm skill.zipInstalls to .claude/skills/git-commits
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Project-specific git commit guidance for Simple History. Use when committing changes, especially across core and premium plugins.Key capabilities
- →Separate changes into logical commits
- →Format commit messages to project standards
- →Manage multi-repository dependency commits
- →Reference related commits across repositories
How it works
The skill enforces a specific commit message structure and logical grouping strategy based on project-specific guidelines for core and premium plugins.
Inputs & outputs
When to use git-commits
- →Split changes into logical commits
- →Format commit messages per repo standards
- →Manage multi-repo dependency commits
- →Review commit history for clarity
About this skill
Git Commits - Project Specifics
Project-specific commit guidance for Simple History.
Multi-Repository Workflow
When changes span core (this repo) and premium (simple-history-premium):
- Commit core first, then premium
- Use related commit messages that reference each other
- Push core before premium when dependencies exist
When to Split Commits
Separate commits:
- CSS vs PHP logic changes
- Different features (even in same file)
- Refactoring vs new functionality
- Multiple independent bug fixes
Single commit:
- Related changes for one feature
- A handler + its CSS
- Tests for the feature being added
Commit Message Style
Follow existing repo style - check git log --oneline -5 for examples.
<summary - what and why>
<optional body with context>
Keep summary concise and descriptive.
When not to use it
- →When committing unrelated changes in a single block
- →When ignoring repository-specific log history
Prerequisites
Limitations
- →Requires manual adherence to project log history
- →Limited to Simple History project guidelines
How it compares
It mandates a multi-repository workflow and specific commit separation rules rather than allowing arbitrary commit styles.
Compared to similar skills
git-commits side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| git-commits (this skill) | 21 | 4mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| git-advanced-workflows | 11 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by bonny
View all by bonny →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.
gh-address-comments
openai
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.