| name | commit |
| description | Git commit guidelines for this project. Use when creating commits, writing commit messages, or preparing changes for version control. Enforces conventional commit format and English language. |
| metadata | {"author":"Alexandre Roman","version":"1.0"} |
Git Commit
Create well-formatted git commits for this project.
Instructions
- Run
git status and git diff --staged to see changes
- If no staged changes, suggest files to stage based on
git diff
- Write a commit message following the rules below
- Execute the commit
Commit Message Rules
- Language: Always write in English
- Format: Use conventional commit format
- Structure:
<type>(<scope>): <subject>
<body>
Co-Authored-By: Claude <noreply@anthropic.com>
Conventional Commit Types
| Type | Description |
|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation only |
| style | Formatting, no code change |
| refactor | Code change, no feature/fix |
| test | Adding or updating tests |
| chore | Build, config, dependencies |
Examples
feat(loyalty): add points expiration feature
Implement automatic points expiration after 12 months of inactivity.
- Add expiration date tracking to LoyaltyState
- Create scheduled workflow for expiration checks
- Send notification email before expiration
Co-Authored-By: Claude <noreply@anthropic.com>
fix(api): handle duplicate transaction IDs
Return 409 Conflict instead of creating duplicate transactions.
Co-Authored-By: Claude <noreply@anthropic.com>
