---
name: git
description: Applies project Git commit message conventions. Use when writing commit messages, reviewing staged changes, or when the user asks for git commit help.
---

# Git Commit Rules

## Type

- `update`: New feature or update feature
- `docs`: Documentation changes
- `refactor`: Code refactoring, test code or add Storybook
- `chore`: Build process or package manager modifications, CI configuration changes

## Subject Rules

- Keep it under 80 characters
- Use present tense
- Don't end with a period
- Use imperative mood
- For long changes, use a list format with bullet points after the main subject

## Body Rules

- Optional
- Explain what and why vs. how
- Wrap at 72 characters
- Use blank line to separate from subject
- For multiple changes, use bullet points

## Important Guidelines

- You must write commit messages in English
- If changes are too many to fit in 80 characters, split into a list format

## Examples

Short format:

```text
update - add authentication component
```

List format for multiple changes:

```text
update - implement user authentication and profile features

- Add OAuth2 login flow with Google and GitHub
- Create user profile management dashboard
- Implement session handling and token refresh
- Add protected route wrapper for authenticated pages
- Set up user preferences storage and sync
```