committing skill
Generates high-quality git commit messages following the conventional commit specification.
- GitHub stars
- 7
- Files
- 2
- Last commit
- May 12, 2026
- License
- MIT
- Allowed tools
- —
What does the committing skill do?
committing generates high-quality git commit messages following the conventional commit specification.
Summary generated from the skill's SKILL.md.
About the committing skill
Generating standardized git commit messages is the primary function of this skill. It assists developers who need to maintain a clean project history by following the conventional commit specification. When an agent is tasked with committing changes, it uses this skill to analyze staged files through git diff commands to understand the nature of the modifications.
The process involves identifying the correct commit type, such as feat, fix, or refactor, and extracting an appropriate scope from the file paths. It produces structured messages that include a subject line in the imperative mood, an optional body for context, and optional footers for breaking changes. This ensures that every commit tells a clear story of what was changed and why, rather than using vague descriptions like fixed stuff or updates.
What an agent can do with it
- 1Create a conventional commit messageAn AI agent can generate a properly formatted commit message after reviewing staged changes.
- 2Identify the correct commit typeThe skill helps determine if a change should be labeled as a feature, a bug fix, or a documentation update.
- 3Detect appropriate commit scopesDevelopers can use the skill to automatically suggest scopes like auth or api based on the files being modified.
- 4Handle breaking changes in historyThe skill provides the correct syntax for marking significant changes that break existing functionality.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the committing skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the committing skill in Plugin
/plugin marketplace add AvinashP/AgentsAtlas /plugin install agents-atlas@agents-atlas
Install the committing skill in Claude Code
~/.claude/skills/committing/SKILL.md
$ npx degit AvinashP/AgentsAtlas/skills/committing ~/.claude/skills/committingInstall the committing skill in Claude Code (project)
.claude/skills/committing/SKILL.md
$ npx degit AvinashP/AgentsAtlas/skills/committing .claude/skills/committingInstall the committing skill in Codex
~/.agents/skills/committing/SKILL.md
$ npx degit AvinashP/AgentsAtlas/skills/committing ~/.agents/skills/committingInstall the committing skill in Gemini CLI
~/.gemini/skills/committing/SKILL.md
$ npx degit AvinashP/AgentsAtlas/skills/committing ~/.gemini/skills/committingInstall the committing skill in Claude.ai
npx degit AvinashP/AgentsAtlas/skills/committing committing && zip -r committing.zip committing # claude.ai → Customize → Skills → + → Create skill → Upload a skill → committing.zip
SKILL.md
View on GitHubCommitting Skill
Create meaningful, conventional commits that tell the story of your changes.
Workflow
1. Analyze Staged Changes
# See what's staged
git diff --staged --stat
# See detailed changes
git diff --staged
Understand the changes:
- What files changed?
- What's the nature of the change?
- Is this one logical change or multiple?
2. Determine Commit Type
| Type | When to Use |
|---|---|
feat |
New feature for users |
fix |
Bug fix for users |
docs |
Documentation only |
style |
Formatting, no code change |
refactor |
Code change, no feature/fix |
perf |
Performance improvement |
test |
Adding/updating tests |
build |
Build system, dependencies |
ci |
CI configuration |
chore |
Maintenance, tooling |
3. Extract Scope (Optional)
Scope identifies the area of the codebase:
feat(auth): add password reset flow
fix(api): handle null response
refactor(cart): extract price calculation
Common scopes:
- Component/module name:
auth,cart,user - Layer:
api,ui,db - Feature area:
checkout,search,settings
4. Write the Message
Format:
<type>(<scope>): <description>
[optional body]
[optional footer]
Description rules:
- Imperative mood: "add" not "added" or "adds"
- Lowercase first letter
- No period at end
- Max 50 characters for subject line
- Explain what and why, not how
5. Verify and Commit
# One more look
git diff --staged
# Commit
git commit -m "type(scope): description"
# Or with body
git commit -m "type(scope): description
More detailed explanation if needed.
Explain why this change was made."
Quick Reference
Good Commit Messages
feat(auth): add two-factor authentication
fix(api): prevent null pointer on empty response
refactor(user): extract validation to separate module
docs(readme): add installation instructions
test(cart): add edge cases for discount calculation
chore(deps): upgrade react to 18.2
Bad Commit Messages
# Too vague
fixed stuff
updates
WIP
# Not imperative
added new feature
fixing bug
# Too long/detailed in subject
feat: add new user authentication system with support for OAuth, SAML, and password-based auth
Commit Scope Detection
Based on changed files:
| File Path | Suggested Scope |
|---|---|
src/auth/* |
auth |
src/components/Button/* |
button or ui |
src/api/* |
api |
tests/* |
usually none |
package.json |
deps |
*.md |
docs |
Breaking Changes
For breaking changes, add ! after type/scope:
feat(api)!: change response format
BREAKING CHANGE: Response now returns { data, meta } instead of raw data.
Multiple Changes
Split into multiple commits when:
- Changes are logically separate
- Different types (fix AND feat)
- Could be reverted independently
Keep together when:
- Changes are related to same feature
- One change requires the other
- Tests for the feature being added
# Stage selectively
git add -p # interactive staging
git add src/feature.ts
git commit -m "feat: add feature"
git add tests/feature.test.ts
git commit -m "test: add tests for feature"
See Also
- examples.md - More commit message examples by scenario
Files in this skill
2committing skill questions
How do I install the committing skill in Claude Code?
Run npx degit AvinashP/AgentsAtlas/skills/committing ~/.claude/skills/committing. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the committing skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How should I format a commit message?
Use the format <type>(<scope>): <description>, followed by an optional body and footer.
What are the rules for the commit description?
The description should use the imperative mood, start with a lowercase letter, have no period at the end, and be a maximum of 50 characters.
How do I indicate a breaking change in a commit?
You can indicate a breaking change by adding an exclamation mark (!) after the type or scope.