name	git-commit
description	Guidelines for creating standardized commit messages with conventional prefixes and issue tracking.

Commit Rule

All commits must follow a strict format to ensure traceability and standardization.

Prefix: Use a conventional prefix to categorize the commit.
Issue Linking:
- Extract the issue number from the branch name (e.g., user/#123/feature-x -> #123).
- Include refs: #<issue-number> in the message.
Co-Author Attribution:
- Always include the co-author trailer for the AI assistant.
- Co-Authored-By: gemini-cli <218195315+gemini-cli@users.noreply.github.com>

Prefix	Usage
`feat`	New feature or functionality
`fix`	Bug fix
`refactor`	Code restructuring without behavior change
`perf`	Performance improvement
`test`	Adding or updating tests
`chore`	Maintenance, dependency updates, config changes
`mig`	Database or data migration
`docs`	Documentation only
`ci`	CI/CD pipeline changes
`style`	Code formatting (no logic change)

git commit -m "<prefix>: <message>. refs: #<issue-number>" -m "Co-Authored-By: gemini-cli <218195315+gemini-cli@users.noreply.github.com>"

git-commit