Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jiatastic avatar

Commit Message

  • 42 installs
  • 7 repo stars
  • Updated January 25, 2026
  • jiatastic/open-python-skills

Helps with git & pull requests tasks.

About

commit-message is a Claude Code skill for git & pull requests. It helps solo builders move faster with AI-assisted development.

  • commit-message
  • Git & Pull Requests
  • AI-coding skill

Commit Message by the numbers

  • 42 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #317 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jiatastic/open-python-skills --skill commit-message

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs42
repo stars7
Last updatedJanuary 25, 2026
Repositoryjiatastic/open-python-skills

What it does

Helps with git & pull requests tasks.

Files

SKILL.mdMarkdownGitHub ↗

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

CommandDescription
--analyzeShow all changed files with status and categories
--batchSuggest how to split changes into multiple commits
--generate [pattern]Generate commit message for matching files
--stagedOnly analyze staged changes (default: all changes)

Commit Types

TypeDescriptionExample
featNew featurefeat(api): add user authentication
fixBug fixfix(db): resolve connection timeout
refactorCode restructuringrefactor(utils): simplify helper functions
docsDocumentationdocs: update README
testTeststest(api): add user endpoint tests
choreMaintenancechore: update dependencies
styleFormattingstyle: fix linting errors

Batch Commit Workflow

When you have multiple unrelated changes:

1. Run --batch to see suggested commit groups 2. Stage files for first commit: git add <files> 3. Commit with suggested message 4. 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 TypeExampleWhen to Use
Feature/Modulecompanion, calendar, inboxChanges to a specific product feature
Platformios, android, webPlatform-specific changes
Integrationoutlook, gmail, slackThird-party integration changes
Componentauth, api, dbCore 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 filefeat(payments): add Stripe webhook handler
fix: fix bugfix(auth): prevent session timeout on mobile
chore: update codechore(ci): reduce build time with parallel jobs
refactor: refactor utilsrefactor(api): extract rate limiting to middleware

Key Principles

1. Read the code - Understand what the changes actually do 2. Identify the feature - What user-facing or system capability is affected? 3. Be specific - Include relevant details (platform, integration, component) 4. Use active voice - "add", "fix", "update", not "added", "fixed", "updated" 5. Keep it concise - First line under 72 characters

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.