commit

name	commit
description	Create git commits from staged changes. Automatically use when the user asks to commit, make a commit, git commit, save changes, or any variation of committing code. Triggers on requests like "commit this", "commit my changes", "/commit", or "make a commit".

Commit

Generate a clear, concise commit message for my uncommitted changes. You must first spawn a new sub-agent for git tasks. Always use Claude Haiku model for this task.

Context

I need a commit message that follows conventional commit format without emojis, written in a natural, human tone. The message should be informative yet brief, capturing what was done and why when relevant.

Format Requirements

Use this structure:

type(scope): #issue_number short descriptive title

- Brief description of what changed
- Why it was changed (if not obvious)
- Any side effects or important notes

Closes #issue_number

Commit Types

• feat: New feature or functionality
• fix: Bug fix or error correction
• perf: Performance improvements
• refactor: Code restructuring without changing functionality
• style: Formatting, spacing, semicolons (no code change)
• docs: Documentation updates
• test: Adding or updating tests
• chore: Maintenance tasks, dependency updates
• build: Build system or external dependency changes
• ci: CI/CD configuration changes
• revert: Reverting a previous commit

Scope Examples

• Component name: feat(UserProfile):
• Module name: fix(auth):
• Feature area: perf(search):
• File type: docs(README):

Guidelines

1. Title line: Maximum 50 characters, imperative mood ("add" not "added")
2. Description:
   • Use bullet points for multiple changes
   • Focus on what and why, not how
   • Keep each line under 72 characters
3. Natural tone: Write like explaining to a colleague
4. Be specific: "Fix null check in payment processing" not "Fix bug"
5. No fluff: Skip obvious things like "Update code" or "Make changes"
6. No AI generated info: Please don't add messages like Generated by Claude Code or AI, and don't add Co-Authored by section. Keep the message clean and follow the guideline given here.

Examples

Feature Addition

feat(checkout): #234 add guest checkout option

- Allow users to complete purchase without account
- Store guest orders with email reference
- Add order lookup by email and order ID

Closes #234

Bug Fix

fix(api): #456 handle timeout errors in payment gateway

- Catch and retry failed payments up to 3 times
- Show user-friendly error after final attempt
- Log detailed errors for debugging

Closes #456

Performance Improvement

perf(dashboard): #789 optimize chart rendering

- Implement virtual scrolling for large datasets
- Reduce re-renders using React.memo
- Load data in 5k chunks instead of all at once

Closes #789

Refactoring

refactor(auth): #321 extract validation logic to helpers

- Move email/password validation to separate utils
- Simplify controller methods
- Improve testability of validation rules

Closes #321

Information Needed

To generate the best commit message, provide:

1. The diff or list of changed files
2. Issue/ticket number (required)
3. Any PRD or task description (if available)
4. Context about why changes were made

Quick Command

"Generate a commit message for issue #[number] with these changes: [paste diff or describe changes]"

Action

use !git commit the staged changes. VERY IMPORTANT note, don't add unstaged changes, only commit the message. Example, you can only RUN: git commit -m [your generated commit message], you should not run git add command, this is to prevent accidental commit of unwanted files to the git. Big security risk. ALWAYS print the generated commit message before running the commit command.

REFERENCE: ./skill-rules-fragment.json