Git Commit

Git Commit

Generates descriptive commit messages following the Conventional Commits specification by analyzing staged changes.

When to use this skill

Use this skill when:

• The user asks to commit changes to the repository
• The user needs help writing commit messages
• Staging and committing code changes
• Following conventional commits format is required

Workflow

1. Check repository status:

   git status
   

2. Review staged and unstaged changes:

   git diff --staged
   git diff
   

3. Review recent commit history for style consistency:

   git log --oneline -10
   

4. Stage relevant files (prefer specific files over git add -A):

   git add <specific-files>
   

5. Generate commit message following the format below

6. Create commit using HEREDOC for proper formatting:

   git commit -m "$(cat <<'EOF'
   <type>(<scope>): <description>
   
   [optional body]
   
   [optional footer]
   EOF
   )"
   

Commit Message Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types

Rules

Subject line:

• Use imperative mood ("add" not "added")
• No period at the end
• Keep under 50 characters (max 72)

Body (optional):

• Use imperative mood
• Wrap lines at 72 characters
• Explain what and why vs. how

Footer (optional):

• Reference issues: Closes #123
• Breaking changes: BREAKING CHANGE: description

Breaking Changes

Indicate breaking changes by:

1. Appending "!" after type/scope: feat(api)!: remove endpoint
2. Footer: BREAKING CHANGE: The endpoint has been removed

Examples

Feature:

feat(auth): add login with google

Bug fix:

fix: prevent infinite loop in user validation

Breaking change:

feat(api)!: remove deprecated endpoint /v1/users

BREAKING CHANGE: The /v1/users endpoint has been removed. Use /v2/users instead.

Documentation:

docs: update readme with setup instructions

With co-author (AI assisted):

feat(templates): add recursive directory copying

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Detailed Reference

For complete Conventional Commits specification details, see references/conventional-commits.md.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.