oma-scm

Use the format type(scope): description, such as feat(auth): add JWT refresh. Keep the subject under 72 characters, use imperative mood, lowercase the first letter, and omit the trailing period. Valid types include feat, fix, refactor, docs, test, chore, style, and perf.

Split commits when changes span different scopes, types, or logically independent features. Stage explicit file paths per commit with git add <specific-files> rather than git add -A, then commit each group with its own Conventional Commit message.

Broad staging can accidentally include unrelated changes or secret files like .env, credentials.json, or *.pem. Staging explicit paths keeps commits reviewable and prevents sensitive material from entering repository history.

Shared history rewrites require explicit maintainer approval before proceeding. If a force-push is unavoidable, use --force-with-lease to avoid overwriting others' work. Local unshared branches can be rebased freely.

Run an onboarding risk scan: check high-churn files, ownership concentration and bus factor, bug hotspot files from fix commits, monthly velocity trends, and revert/hotfix frequency. Thresholds are configurable in cm-config.yaml under onboarding_metrics.

Use the quick path for ordinary commits: stage explicit files, validate the message, and stop. Use the full CM path when work involves branching strategy, merges, rebases, cherry-picks, worktrees, releases, CODEOWNERS, or audit requirements.