Git Commit Smart

majiayu000/git-commit-smart

Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.

1k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

242

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/majiayu000/spellbook --skill git-commit-smart

The instruction itself

22 sections, as written by the author

Smart Git Commit

> Inspired by claude-code-plugins-plus

Purpose

Automatically generate meaningful commit messages by analyzing staged changes, following conventional commit format.

Commit Message Format

<type>(<scope>): <subject>

<body>

<footer>

Types

| Type | Description |

|------|-------------|

| feat | New feature |

| fix | Bug fix |

| docs | Documentation only |

| style | Formatting, no code change |

| refactor | Code change, no new feature or fix |

| perf | Performance improvement |

| test | Adding/updating tests |

| chore | Maintenance tasks |

| ci | CI/CD changes |

| build | Build system changes |

Scope

Optional, indicates the section of codebase:

auth, api, ui, db, config, etc.

Subject

Imperative mood ("add" not "added")
No period at end
Max 50 characters
Lowercase

Body

Explain WHAT and WHY, not HOW
Wrap at 72 characters
Separate from subject with blank line

Breaking changes: BREAKING CHANGE: description
Issue references: Closes #123, Fixes #456

Workflow

1. Analyze Changes

# View staged changes
git diff --staged

# View changed files
git diff --staged --name-only

# View stats
git diff --staged --stat

2. Determine Type

Based on changes:

New files with features → feat
Modified files fixing issues → fix
Only .md files → docs
Only test files → test
package.json, configs → chore or build

3. Identify Scope

Look at file paths:

src/auth/* → scope: auth
src/api/* → scope: api
tests/* → scope: test
Multiple areas → omit scope or use broader term

4. Write Subject

Summarize the change:

feat(auth): add OAuth2 login support
fix(api): handle null response in user endpoint
docs: update README with installation steps
refactor(db): extract query builder to separate module

5. Write Body (if needed)

For complex changes:

feat(auth): add OAuth2 login support

Implement OAuth2 authentication flow with support for
Google and GitHub providers. This allows users to sign
in without creating a separate account.

- Add OAuth2 client configuration
- Implement callback handlers
- Store OAuth tokens securely
- Add provider selection UI

Examples

Simple Feature

feat(ui): add dark mode toggle

Bug Fix with Issue Reference

fix(api): prevent duplicate user creation

Check for existing email before inserting new user record.
Race condition could cause duplicate entries when requests
arrived simultaneously.

Fixes #234

Breaking Change

feat(api)!: change response format to JSON:API

BREAKING CHANGE: All API responses now follow JSON:API
specification. Clients must update their parsers.

Migration guide: docs/migration-v2.md

Multiple Files, Single Purpose

refactor: extract validation logic to shared module

Move duplicate validation code from controllers to
a shared validation module. Reduces code duplication
and ensures consistent validation across endpoints.

Anti-Patterns to Avoid

❌ "fix stuff"
❌ "update code"
❌ "WIP"
❌ "changes"
❌ "fixed bug"
❌ "misc updates"
❌ Commits with 50+ files and vague message

Best Practices

Atomic commits - One logical change per commit
Meaningful messages - Future you will thank present you
Reference issues - Link to tickets/issues when relevant
Review before commit - git diff --staged always
Don't commit secrets - Check for API keys, passwords

Quick Reference

# Stage specific files
git add <file>

# Stage all changes
git add -A

# Interactive staging
git add -p

# Commit with message
git commit -m "type(scope): subject"

# Commit with body
git commit -m "type(scope): subject" -m "body paragraph"

# Amend last commit
git commit --amend

How to use it

Copy the folder

Take majiayu000/git-commit-smart from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.