Commitlint Guidelines

We use Conventional Commits to standardize commit messages and automate tooling.

Format

<type>(<optional scope>): <subject>

Types

• feat, fix, perf, refactor, docs, style, test, build, ci, chore, revert

Scopes

• Optional; use app/package names when helpful, e.g. server, client, ui

Examples

• feat(subscription): add webhook retries
• fix(client): handle Windows path resolution
• ci(actions): improve pnpm caching keys