git-commit-brief

To write conventional commit messages, format them as `<type>(<scope>): <subject>` with a required type and lowercase scope. This standard keeps your git commit history readable and actionable for day-to-day codebase documentation.

The correct scope in a conventional commit is a lowercase identifier such as `core`, `module`, `test`, `dev`, `agent`, or `docs`. Selecting a valid scope helps categorize the specific area of the codebase your commit targets.

To avoid low-value details in your git commit history, exclude process-oriented metadata like review steps or backlog task IDs. Focus the commit subject on describing the actual code change and its outcome.

Yes, you can use conventional commits for documentation and test changes across your codebase. Standardizing the commit format works for day-to-day development across code, docs, tests, and agent-related changes.

The best way to standardize an outcome-focused commit subject is to describe what the code change actually achieves. Avoid process metadata and ensure the format follows the `<type>(<scope>): <subject>` structure for consistency.