v1.5.0

Added

• commit command — generate a commit message and commit. commitbrief commit reads your staged diff, asks the configured provider for a commit message, shows it for confirmation, and — on Yes (the default) or --yes — runs git commit. This is the first path where the tool writes to git; every review path stays read-only (the PRD’s read-only rule is rescoped to the review path). See ADR-0019.
  • --type / -t picks the format: plain (default), conventional, conventional+body, gitmoji, subject+body.
  • --generate / -g <N> offers N alternatives (1–10) in an arrow-key selector; a single provider call produces all N.
  • --provider / --model / --cli select the backend exactly as for a review. Messages are always written in English regardless of --lang.
  • The pre-send .commitbrief/** guard, secret scan, and cost preflight all run on the staged diff before the call; the suggestion is cached.
  • With no staged changes it errors clearly; a non-TTY run without --yes errors (it cannot confirm). --yes commits the first suggestion and does not bypass the secret scan or cost preflight.
  • New config keys commit.type and commit.generate set the defaults (precedence: flag > config > built-in). This complements the existing read-only --suggest-commit review flag, which is unchanged.

Changed

• remote pr no longer requests changes by default. A request-changes verdict is now opt-in: --request-changes-on defaults to unset instead of critical. Without the flag, remote pr submits approve (no findings or info-only) or comment (any non-info findings) and never request-changes. Pass --request-changes-on=<critical|high|medium|low> to re-enable escalation at or above that severity. Inline-comment posting and the comment-volume cap are unchanged. Auto-requesting changes should be a deliberate choice, not the out-of-the-box behavior (ADR-0016 §5 Update). Verdict-only — no effect under --no-post.