// Use when creating git commits, writing commit messages, or following version control workflows
| name | conventional-commits |
| description | Use when creating git commits, writing commit messages, or following version control workflows |
Structured commit message format for version control that provides clear, readable project history.
The Conventional Commits specification provides:
| Type | Use For | Version Bump |
|---|---|---|
feat | New feature | MINOR |
fix | Bug fix | PATCH |
docs | Documentation only | PATCH |
style | Formatting, no logic change | PATCH |
refactor | Code restructuring, no behavior change | PATCH |
perf | Performance improvement | PATCH |
test | Adding or updating tests | PATCH |
build | Build system or dependencies | PATCH |
ci | CI/CD configuration | PATCH |
chore | Maintenance, no user-facing change | PATCH |
revert | Revert a previous commit | PATCH |
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Rules:
(api), auth), parser)feat: add user authentication
Implement JWT-based authentication with login/logout endpoints.
Includes password hashing and session management.
Closes: #123
fix(api): handle null response from server
Previous implementation crashed when server returned null.
Now returns empty result set.
Assisted-by: GLM 4.6 via Claude Code
feat(storage)!: change bucket listing API
BREAKING CHANGE: bucket list now returns async iterator
instead of array. Update all callers to use for-await.
refactor(core): simplify error handling
Consolidate duplicate error handlers into single utility.
No behavior changes - internal cleanup only.
revert: feat(auth): add OAuth support
This reverts commit 8b5a1c2. OAuth provider changed
their API and we need to redesign integration.
Indicate breaking changes in two ways:
Option 1: Add ! after type/scope
feat(api)!: remove deprecated endpoint
Option 2: Add BREAKING CHANGE: footer
feat(api): remove deprecated endpoint
BREAKING CHANGE: endpoint no longer exists. Use newEndpoint instead.
AI agents must disclose their assistance in the commit footer:
Assisted-by: [Model Name] via [Tool Name]
Examples:
Assisted-by: GLM 4.6 via Claude CodeAssisted-by: Claude Opus 4.5 via claude.ai| Mistake | Why Wrong | Correct |
|---|---|---|
Added login feature | Past tense, capitalized | feat: add login feature |
fix bug. | Trailing period | fix: resolve login error |
update | Missing type | chore: update dependencies |
feature:add-auth | Missing space after colon | feat: add authentication |
FEAT: big change | Uppercase type | feat: add authentication |
| Multi-line description no blank line | No separation | Add blank line after subject |
feat(summarization): add support for nested bullet points
Previous implementation only flattened all content. Now preserves
hierarchy by respecting indentation levels. Users can now create
structured summaries with parent-child relationships.
Closes: #456
Use footers for:
BREAKING CHANGE: detailed explanationCloses: #123, Fixes: #456, Refs: #789Assisted-by: Model via ToolMultiple footers separated by blank lines:
feat: add batch upload
Implements multipart upload for large files.
BREAKING CHANGE: upload() signature changed - now requires options object
Closes: #123
Assisted-by: GLM 4.6 via Claude Code
Required flag: Always use --signoff when committing:
git commit --signoff -m "feat: add user authentication"
The --signoff flag adds a Signed-off-by trailer to the commit message, indicating the committer has certified the commit follows developer certificate of origin (DCO).
Before committing, verify:
! or footer--signoff flagCreate new blogposts from a template or linkposts using the hydrate command.
Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, or branch creation via Neon CLI or Neon MCP. Triggers include "Neon branch", "test migrations safely", "branch production data", "schema-only branch", "reset branch" and "sensitive data testing".
Read files without making changes. Use when you need read-only file access.
Create reusable templ UI components with props, children, and composition patterns. Use when building UI components, creating component libraries, mentions 'button component', 'card component', or 'reusable templ components'.
Build interactive hypermedia-driven applications with templ and HTMX. Use when creating dynamic UIs, real-time updates, AJAX interactions, mentions 'HTMX', 'dynamic content', or 'interactive templ app'.
Integrate templ components with Go HTTP server using net/http. Use when connecting templ to web server, creating HTTP handlers, mentions 'templ server', 'HTTP routes', or 'serve templ components'.