Git Commit Format Skill
Generates a commit message (title + description) from a description of changes.
Conventions
Commit Title
Follows Conventional Commits spec:
{type}({optional scope}): {short imperative description}
- Types:
feat, fix, chore, refactor, docs, style, test, perf, ci, build, revert
- Use imperative mood: "add", "fix", "remove" — not "added", "fixed", "removed"
- Max ~72 characters
- All lowercase except proper nouns
- No period at the end
- Example:
feat(auth): add biometric login support
Commit Description
Bullet list using past tense action words:
* Fixed ...
* Added ...
* Changed ...
* Removed ...
- Only include bullets that apply to the actual changes
- Keep each bullet concise and specific
- Allowed verbs:
Fixed, Added, Changed, Removed, Updated, Refactored, Migrated, Deprecated
- Always in English
- Never include
Co-Authored-By, Signed-off-by, or any trailer attributing the commit to an AI agent or tool
Type Selection Guide
| Type |
When to use |
feat |
New functionality |
fix |
Bug fix |
refactor |
Code change with no behavior change |
chore |
Config, deps, tooling, maintenance |
test |
Adding or updating tests |
docs |
Documentation only |
style |
Formatting, whitespace |
perf |
Performance improvement |
ci |
CI/CD changes |
build |
Build system changes |
revert |
Reverting a previous commit |
If the changes span multiple concerns, suggest splitting into separate commits.
Output Format
feat(flutter): upgrade Flutter SDK to v3.19
* Updated Flutter SDK version to 3.19
* Changed minimum iOS deployment target to 14.0
* Fixed deprecated API usages after upgrade
* Removed unused legacy plugins
The commit message must end after the bullet list. Do not append any Co-Authored-By, Signed-off-by, or AI attribution trailers.
Examples
User: "I upgraded Flutter and had to fix some deprecated APIs and update the iOS target"
feat(flutter): upgrade Flutter SDK to v3.19
* Updated Flutter SDK version to 3.19
* Changed minimum iOS deployment target to 14.0
* Fixed deprecated API usages after upgrade
User: "Fixed a crash on login when the user has no internet"
fix(auth): handle login crash when offline
* Fixed crash on login screen when no internet connection is available
* Added offline error state to login flow
1---2name: git-commit-format3description: Generates properly formatted Git commit messages (title + description) following Conventional Commits. Use this skill whenever the user wants to write a commit message, document code changes in git format, or asks things like "how should I commit this?", "write a commit for these changes", "help me with my commit message", or describes what they changed and needs a git-ready output. Always use this skill when the user describes code changes and needs a commit, even if they don't explicitly say "commit".4---56# Git Commit Format Skill78Generates a **commit message** (title + description) from a description of changes.910---1112## Conventions1314### Commit Title1516Follows **Conventional Commits** spec:1718```19{type}({optional scope}): {short imperative description}20```2122- **Types:** `feat`, `fix`, `chore`, `refactor`, `docs`, `style`, `test`, `perf`, `ci`, `build`, `revert`23- Use imperative mood: "add", "fix", "remove" — not "added", "fixed", "removed"24- Max ~72 characters25- All lowercase except proper nouns26- No period at the end27- Example: `feat(auth): add biometric login support`2829### Commit Description3031Bullet list using past tense action words:3233```34* Fixed ...35* Added ...36* Changed ...37* Removed ...38```3940- Only include bullets that apply to the actual changes41- Keep each bullet concise and specific42- Allowed verbs: `Fixed`, `Added`, `Changed`, `Removed`, `Updated`, `Refactored`, `Migrated`, `Deprecated`43- Always in **English**44- **Never** include `Co-Authored-By`, `Signed-off-by`, or any trailer attributing the commit to an AI agent or tool4546---4748## Type Selection Guide4950| Type | When to use |51|------|-------------|52| `feat` | New functionality |53| `fix` | Bug fix |54| `refactor` | Code change with no behavior change |55| `chore` | Config, deps, tooling, maintenance |56| `test` | Adding or updating tests |57| `docs` | Documentation only |58| `style` | Formatting, whitespace |59| `perf` | Performance improvement |60| `ci` | CI/CD changes |61| `build` | Build system changes |62| `revert` | Reverting a previous commit |6364If the changes span multiple concerns, suggest splitting into separate commits.6566---6768## Output Format6970```71feat(flutter): upgrade Flutter SDK to v3.197273* Updated Flutter SDK version to 3.1974* Changed minimum iOS deployment target to 14.075* Fixed deprecated API usages after upgrade76* Removed unused legacy plugins77```7879> The commit message must end after the bullet list. Do **not** append any `Co-Authored-By`, `Signed-off-by`, or AI attribution trailers.8081---8283## Examples8485**User:** "I upgraded Flutter and had to fix some deprecated APIs and update the iOS target"8687```88feat(flutter): upgrade Flutter SDK to v3.198990* Updated Flutter SDK version to 3.1991* Changed minimum iOS deployment target to 14.092* Fixed deprecated API usages after upgrade93```9495---9697**User:** "Fixed a crash on login when the user has no internet"9899```100fix(auth): handle login crash when offline101102* Fixed crash on login screen when no internet connection is available103* Added offline error state to login flow104```