Back to Hermes Agent

Conventional Commits Quick Reference

skills/github/github-pr-workflow/references/conventional-commits.md

2026.6.52.4 KB
Original Source

Conventional Commits Quick Reference

Format: type(scope): description

Types

TypeWhen to useExample
featNew feature or capabilityfeat(auth): add OAuth2 login flow
fixBug fixfix(api): handle null response from /users endpoint
refactorCode restructuring, no behavior changerefactor(db): extract query builder into separate module
docsDocumentation onlydocs: update API usage examples in README
testAdding or updating teststest(auth): add integration tests for token refresh
ciCI/CD configurationci: add Python 3.12 to test matrix
choreMaintenance, dependencies, toolingchore: upgrade pytest to 8.x
perfPerformance improvementperf(search): add index on users.email column
styleFormatting, whitespace, semicolonsstyle: run black formatter on src/
buildBuild system or external depsbuild: switch from setuptools to hatch
revertReverts a previous commitrevert: revert "feat(auth): add OAuth2 login flow"

Scope (optional)

Short identifier for the area of the codebase: auth, api, db, ui, cli, etc.

Breaking Changes

Add ! after type or BREAKING CHANGE: in footer:

feat(api)!: change authentication to use bearer tokens

BREAKING CHANGE: API endpoints now require Bearer token instead of API key header.
Migration guide: https://docs.example.com/migrate-auth

Multi-line Body

Wrap at 72 characters. Use bullet points for multiple changes:

feat(auth): add JWT-based user authentication

- Add login/register endpoints with input validation
- Add User model with argon2 password hashing
- Add auth middleware for protected routes
- Add token refresh endpoint with rotation

Closes #42

Linking Issues

In the commit body or footer:

Closes #42          ← closes the issue when merged
Fixes #42           ← same effect
Refs #42            ← references without closing
Co-authored-by: Name <email>

Quick Decision Guide

  • Added something new? → feat
  • Something was broken and you fixed it? → fix
  • Changed how code is organized but not what it does? → refactor
  • Only touched tests? → test
  • Only touched docs? → docs
  • Updated CI/CD pipelines? → ci
  • Updated dependencies or tooling? → chore
  • Made something faster? → perf