메뉴
Use when writing git commit messages, reviewing commits, or setting up commit conventions. Triggers on commit, git commit, commit message, changelog, semantic versioning.
| name | conventional-commits |
| description | Use when writing git commit messages, reviewing commits, or setting up commit conventions. Triggers on commit, git commit, commit message, changelog, semantic versioning. |
Structured commit messages that enable automated changelogs and semantic versioning.
<type>[optional scope]: <description>
[optional body]
[optional footer]
| Type | Purpose | SemVer Impact |
|---|---|---|
feat | New feature (MUST use for new features) | MINOR bump |
fix | Bug fix (MUST use for bug fixes) | PATCH bump |
docs | Documentation only | None |
style | Formatting, no code change | None |
refactor | Neither fix nor feature | None |
perf | Performance improvement | None |
test | Adding/fixing tests | None |
chore | Build, tooling, deps | None |
Any + BREAKING CHANGE | Breaking API change | MAJOR bump |
feat, fix, etc.) followed by colon and spacefeat MUST be used when a commit adds a new featurefix MUST be used when a commit represents a bug fixfix(parser):token: value or token #value formatBREAKING CHANGE: (or BREAKING-CHANGE:) followed by a spaceBREAKING CHANGE:feat and fix MAY be used! MAY be appended after type/scope (with or without scope: feat!: or feat(scope)!:) to draw attention to breaking change. BREAKING CHANGE: in footer MUST also be included when ! is usedSimple feature:
feat: add email notifications for order updates
Scoped bug fix:
fix(auth): prevent session fixation on login
Breaking change with ! and footer:
refactor(api)!: remove deprecated /v1 endpoints
Migrate all clients to /v2 before upgrading.
BREAKING CHANGE: /v1/* endpoints have been removed. Use /v2/* instead.
Breaking change without scope (using !):
feat!: drop Node 14 support
BREAKING CHANGE: minimum Node version is now 16.
Multiple footers:
feat(parser): support nested array syntax
Arrays can now contain other arrays, enabling complex
data structures in configuration files.
Reviewed-by: Alice
Closes #245
| Mistake | Correct |
|---|---|
Fixed bug in login | fix(auth): resolve null check on login |
feat: Fix typo | fix: correct typo in README (not a feature) |
BREAKING CHANGE without footer format | Must be at start of footer/body: BREAKING CHANGE: description |
feat!: without BREAKING CHANGE in footer | Rule 11: ! requires BREAKING CHANGE: in footer too |
| Missing blank line before body | Body MUST be separated by one blank line |
Scope with spaces feat(my scope): | Use hyphens: feat(my-scope): |
Universal coding standards, best practices, and patterns. Use when developing in any language — triggers on TypeScript, JavaScript, React, Node.js, Python, Nix, ruff, pyright, pytest, uv, flake.nix, justfile, just, recipes, and general code quality topics.
A formal evaluation framework for Claude Code sessions, implementing eval-driven development (EDD) principles.
Audit NixOS impermanence configuration — find files on root filesystem not covered by persistence declarations. Use when the user wants to check for untracked files, audit impermanence, or runs /impermanence-audit.
Docker-in-Docker with network_mode host for multi-node simulation
Use when implementing LangGraph workflows that need to pause for user input or external confirmation before continuing execution
Workaround for @nuxt/eslint not auto-detecting TypeScript, causing vue-eslint-parser to fail on <script lang="ts"> blocks