Commit message

Skill jiatastic/open-python-skills/skills/commit-message

Analyze git changes and generate conventional commit messages. Supports batch commits for multiple unrelated changes. Use when: (1) Creating git commits, (2) Reviewing staged changes, (3) Splitting large changesets into logical commits.From its SKILL.md

Install

npx -y skills add jiatastic/open-python-skills --skill commit-message

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
runs commandsInstructs the agent to run 5 commands, including `python3 .shared/commit-message/scripts/analyze_changes.py --analyze` and 4 more.

SKILL.md

5.0 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

commit-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 --batch to 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.py script provides file grouping and basic suggestions. Use its output as a starting point, then read git diff to 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

What ships with it: 2 files

13.3 KB alongside SKILL.md, 1 of them executable

data/

commit_patterns.json2.6 KB

scripts/

analyze_changes.pyruns10.7 KB

Gives 1 of the 12 instructions most pr commit review skills give in ~1.1k tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formathere, and in 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

analyze actual code changes to infer business context
describe what changes accomplish rather than listing files
use active voice for commit descriptions
use business modules or features as commit scope
run batch command to identify logical commit groups

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.