name: commit description: This skill should be used when the user asks to "create a commit", "commit changes", "write a commit message", "make a commit", needs help with "conventional commits", or wants to understand commit message format and best practices.

Conventional Commit Guidelines

Guidance for creating well-structured commit messages following the Conventional Commits specification.

Commit Workflow

1. Run git status and git diff to analyze changes
2. If there are unstaged changes to include, stage them with git add
3. Check recent commits with git log --oneline -5 for style reference
4. Determine the appropriate commit type based on the nature of changes
5. Write a concise commit message in imperative mood
6. Create the commit

Commit Message Structure

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Writing Good Commit Messages

Description Guidelines

• Use imperative mood ("add feature" not "added feature")
• Keep under 50 characters when possible
• Do not end with a period
• Focus on the "what" and "why", not the "how"

Examples

Good:

feat: add user authentication endpoint
fix: resolve null pointer in data parser
refactor: extract validation logic to helper
docs: update API documentation for v2
chore: update dependencies to latest versions

With scope:

feat(auth): add OAuth2 support
fix(parser): handle empty input gracefully
refactor(api): simplify request handling

With body:

feat: add rate limiting to API endpoints

Implement token bucket algorithm for rate limiting.
Default limit is 100 requests per minute per user.

Closes #123

Breaking Changes

Mark breaking changes with an exclamation mark (!) after type/scope:

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

Or include BREAKING CHANGE: in the footer:

feat: update authentication flow

BREAKING CHANGE: JWT tokens now expire after 1 hour instead of 24 hours