---

name: knowns.commit description: Use when committing code changes with proper conventional commit format and verification

Committing Changes

Your task is to help the user to generate a commit message and commit the changes using git.

Guidelines

• DO NOT add any ads such as "Generated with Claude Code"
• DO NOT add Co-Authored-By line
• Only generate the message for staged files/changes
• Don't add any files using git add. The user will decide what to add.
• Follow the rules below for the commit message.

Format

Copy<type>:<space><message title>

<bullet points summarizing what was updated>

Example Titles

Copyfeat(auth): add JWT login flow
fix(ui): handle null pointer in sidebar
refactor(api): split user controller logic
docs(readme): add usage section

Example with Title and Body

Copyfeat(auth): add JWT login flow

- Implemented JWT token validation logic
- Added documentation for the validation component

Rules

• Title is lowercase, no period at the end.
• Title should be a clear summary, max 50 characters.
• Use the body (optional) to explain why, not just what.
• Bullet points should be concise and high-level.

Avoid:

• Vague titles like: "update", "fix stuff"
• Overly long or unfocused titles
• Excessive detail in bullet points

Allowed Types

Process

1. Run git status and git diff --staged to see staged changes
2. Generate commit message following the format above
3. Show the message to user and ask for confirmation
4. Commit with git commit -m "message"