commit-message skill
scriptsAnalyze git changes to generate context-aware commit messages following the Conventional Commits specification.
- GitHub stars
- 10
- Files
- 3
- Last commit
- Jan 25, 2026
- License
- MIT
- Allowed tools
- —
What does the commit-message skill do?
commit-message analyzes git changes to generate context-aware commit messages following the Conventional Commits specification.
Summary generated from the skill's SKILL.md.
About the commit-message skill
Generating standardized git commit messages from code changes is the primary function of this skill. Developers use it to transform raw git diffs into structured messages that follow the Conventional Commits specification, including types like feat, fix, refactor, and chore. It is particularly useful when an agent needs to review staged changes or split large, messy changesets into smaller, logical commits.
An agent loads this skill by running the analyze_changes.py script with specific flags. The --analyze command identifies changed files and categories, while the --batch command suggests how to group unrelated changes into separate commits. Users can also target specific files using the --generate command with a file pattern. The tool relies on analyzing file status, directories, and semantic relationships to suggest appropriate scopes such as specific business modules, platforms, or integrations.
What an agent can do with it
- 1Split large changesetsA developer can use the batch command to organize multiple unrelated code changes into distinct, logical commit groups.
- 2Generate specific commit messagesYou can request a commit message for a specific set of files using a file pattern.
- 3Review staged changesAn agent can analyze only the files that have been staged for a commit to prepare a message.
- 4Categorize file changesThe tool provides a summary of all changed files along with their current status and categories.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the commit-message 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 commit-message skill in Plugin
/plugin marketplace add jiatastic/open-python-skills /plugin install open-python-skills@open-python-skills
Install the commit-message skill in Claude Code
~/.claude/skills/commit-message/SKILL.md
$ npx degit jiatastic/open-python-skills/skills/commit-message ~/.claude/skills/commit-messageInstall the commit-message skill in Claude Code (project)
.claude/skills/commit-message/SKILL.md
$ npx degit jiatastic/open-python-skills/skills/commit-message .claude/skills/commit-messageInstall the commit-message skill in Codex
~/.agents/skills/commit-message/SKILL.md
$ npx degit jiatastic/open-python-skills/skills/commit-message ~/.agents/skills/commit-messageInstall the commit-message skill in Gemini CLI
~/.gemini/skills/commit-message/SKILL.md
$ npx degit jiatastic/open-python-skills/skills/commit-message ~/.gemini/skills/commit-messageInstall the commit-message skill in Claude.ai
npx degit jiatastic/open-python-skills/skills/commit-message commit-message && zip -r commit-message.zip commit-message # claude.ai → Customize → Skills → + → Create skill → Upload a skill → commit-message.zip
SKILL.md
View on GitHubcommit-message
Analyze git changes and generate context-aware commit messages following Conventional Commits.
Quick Start
# Analyze all changes
python3 .shared/commit-message/scripts/analyze_changes.py --analyze
# Get batch commit suggestions
python3 .shared/commit-message/scripts/analyze_changes.py --batch
# Generate message for specific files
python3 .shared/commit-message/scripts/analyze_changes.py --generate "src/api/*.py"
Commands
| Command | Description |
|---|---|
--analyze |
Show all changed files with status and categories |
--batch |
Suggest how to split changes into multiple commits |
--generate [pattern] |
Generate commit message for matching files |
--staged |
Only analyze staged changes (default: all changes) |
Commit Types
| Type | Description | Example |
|---|---|---|
feat |
New feature | feat(api): add user authentication |
fix |
Bug fix | fix(db): resolve connection timeout |
refactor |
Code restructuring | refactor(utils): simplify helper functions |
docs |
Documentation | docs: update README |
test |
Tests | test(api): add user endpoint tests |
chore |
Maintenance | chore: update dependencies |
style |
Formatting | style: fix linting errors |
Batch Commit Workflow
When you have multiple unrelated changes:
- Run
--batchto see suggested commit groups - Stage files for first commit:
git add <files> - Commit with suggested message
- Repeat for remaining groups
Grouping Strategy
Files are grouped by:
- Directory/Module:
src/api/,tests/,docs/ - Change Type: Added vs Modified vs Deleted
- Semantic Relationship: Related files together
Context-Aware Commit Messages
Note: The
analyze_changes.pyscript provides file grouping and basic suggestions. Use its output as a starting point, then readgit diffto understand the actual changes and generate context-aware messages following the examples below.
When generating commit messages, analyze the actual code changes to infer business context. Don't just describe files—describe what the changes accomplish.
Scope Guidelines
The scope should reflect the business module or feature, not just the directory:
| Scope Type | Example | When to Use |
|---|---|---|
| Feature/Module | companion, calendar, inbox |
Changes to a specific product feature |
| Platform | ios, android, web |
Platform-specific changes |
| Integration | outlook, gmail, slack |
Third-party integration changes |
| Component | auth, api, db |
Core infrastructure changes |
Input/Output Examples
Example 1: New Feature
Input (code changes):
+ src/companion/pages/AvailabilityDetailPage.tsx
+ src/companion/pages/AvailabilityActionsPage.tsx
+ src/companion/components/AvailabilityCard.tsx
M src/companion/navigation/routes.ts
Output:
feat(companion): add availability detail and actions pages for ios
- New AvailabilityDetailPage showing time slot details
- New AvailabilityActionsPage for booking/canceling
- AvailabilityCard component for list display
- Updated navigation routes
Example 2: Bug Fix
Input (code changes):
M src/integrations/outlook/email_sender.py
M src/integrations/outlook/auth.py
Output:
fix(outlook): resolve email sending failures due to token expiration
Refresh OAuth token before sending when close to expiry
Example 3: Multi-platform Change
Input (code changes):
M ios/Calendar/CalendarView.swift
M android/calendar/CalendarFragment.kt
M web/src/calendar/Calendar.tsx
Output:
feat(calendar): add week view across all platforms
Implement consistent week view UI for iOS, Android, and web
Example 4: Chore/Maintenance
Input (code changes):
M package.json
M yarn.lock
M requirements.txt
Output:
chore(deps): update dependencies to latest versions
Writing Good Descriptions
| Bad (Generic) | Good (Context-Aware) |
|---|---|
feat: add new file |
feat(payments): add Stripe webhook handler |
fix: fix bug |
fix(auth): prevent session timeout on mobile |
chore: update code |
chore(ci): reduce build time with parallel jobs |
refactor: refactor utils |
refactor(api): extract rate limiting to middleware |
Key Principles
- Read the code - Understand what the changes actually do
- Identify the feature - What user-facing or system capability is affected?
- Be specific - Include relevant details (platform, integration, component)
- Use active voice - "add", "fix", "update", not "added", "fixed", "updated"
- Keep it concise - First line under 72 characters
Files in this skill
3commit-message skill questions
How do I install the commit-message skill in Claude Code?
Run npx degit jiatastic/open-python-skills/skills/commit-message ~/.claude/skills/commit-message. 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 commit-message 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.
What are the different types of commit messages supported?
The tool supports types such as feat, fix, refactor, docs, test, chore, and style.
How should I choose a scope for my commit message?
The scope should reflect the business module, platform, integration, or core component being changed.