Git Commit Conventions

Commit Message Format

[PM-XXXXX] <type>: <imperative summary>

<optional body explaining why, not what>

Rules

1. Ticket prefix: Always include [PM-XXXXX] matching the Jira ticket
2. Type keyword: Read ${CLAUDE_PLUGIN_ROOT}/references/change-type-labels.md for the full table of conventional commit types and their CI label mappings. If the type cannot be confidently determined, ask the user.

Examples

[PM-12345] feat: Add biometric unlock timeout configuration

Users reported confusion about when biometric prompts appear.
This adds a configurable timeout setting to the security preferences.

Ambiguous cases — choosing between similar types:

# Refactor that also fixes a bug? Use the primary intent:
[PM-12345] fix: Resolve null pointer in vault sync retry logic

# Test-only change:
[PM-12345] test: Add unit tests for biometric timeout edge cases

Followup Commits

Only the first commit on a branch needs the full format (ticket prefix, type keyword, body). Subsequent commits can use a short, descriptive summary with no prefix or body required.

Update error handling in login flow

Pre-Commit Quality Gate

Before staging, run the perform-preflight skill for the full quality gate checklist (tests, lint, security, architecture). Consult the repo's CLAUDE.md for platform-specific build and lint commands.