git-commit

Git Commit

Git commit message generation skill, automatically generates standardized commit messages based on code changes.

Git commit message generator that creates conventional commit messages based on code changes.

When to Use

Use this skill when the user requests the following operations:

• Generate commit message / Generate commit message
• Write commit message / Write commit message
• Commit code / Commit code
• Describe code changes / Describe code changes

Instructions

Commit Message Format / Commit Message Format

Follow the Conventional Commits specification:

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

<body>

<footer>

Types / Types

Type	Description / Description
feat	New feature / New feature
fix	Bug fix / Bug fix
docs	Documentation / Documentation
style	Formatting / Formatting
refactor	Refactoring / Refactoring
perf	Performance / Performance
test	Tests / Tests
chore	Build/tools / Build/tools

Generation Steps / Generation Steps

1. Analyze changes - View git diff or git status
2. Determine type - Choose an appropriate type based on the changes
3. Extract scope - Determine the affected module or component
4. Write subject - Describe the change in concise language (within 50 characters)
5. Add body - If needed, explain the reason and impact of the change in detail

Rules / Rules

• The subject line must not exceed 50 characters
• Use the imperative mood (e.g. "add" instead of "added")
• The first letter of the subject line is lowercase
• Do not add a period at the end of the subject line
• Each line of the body must not exceed 72 characters

Examples

Example 1: New feature

feat(auth): add OAuth2 login support

- Add Google OAuth2 provider
- Add GitHub OAuth2 provider
- Update login page with social login buttons

Example 2: Bug fix

fix(api): resolve null pointer in user service

The getUserById method was not handling the case when
user doesn't exist, causing a NullPointerException.

Closes #123

Example 3: Documentation update

docs(readme): update installation instructions

Add Docker setup guide and clarify environment variables.

Example 4: Refactoring

refactor(database): migrate from callbacks to async/await

Convert all database operations to use async/await pattern
for better readability and error handling.