commit-discipline

Use a single heredoc with git commit -m containing an imperative subject under 50 chars, a WHY paragraph of 60+ chars, and contiguous trailers (Slice, Tests, Red-then-green, Verified) at the bottom. Multiple -m flags fail because git interpret-trailers only reads the last paragraph.

The failure is almost always structural, not the token itself. Multiple -m flags split trailers into separate paragraphs that git interpret-trailers cannot see, and embedded newlines inside a -m argument truncate the extracted body. Use the canonical heredoc form instead.

Yes, git commit --no-verify bypasses the git-native hook, but the post-commit hook detects the bypass via a trace-file recency check and logs it to git-discipline-no-verify.log for later audit. There is no magic-comment bypass at the git-native layer.

Eight Slice opt-out tokens relax the rules: docs-only, config-only, migration-only, spec-only, chore-deps, revert, merge, and wip. These drop the Tests requirement, and the first five also drop Red-then-green; wip commits are accepted locally but blocked at push.

The Visual trailer is required when the staged diff touches UI files: web templates, stylesheets, storyboards, asset catalogs, or Swift files importing SwiftUI/UIKit. Backend-only commits skip it, and false positives can use Visual: n/a with a rationale from the closed enum.

Yes, through backstop layers. A post-rewrite hook validates rewritten bodies with warn-and-log (git ignores its exit status), and pre-push re-validates every commit body in the push range as the final gate before code reaches a remote.