Compose Conventional Commits 1.0.0 messages — `type(scope): subject`, body explains the why, breaking changes flagged. Read the diff first, match the project's prior types and scopes, never bundle unrelated changes.
Draft motebit/<name>@<version> specifications with the foundation-law markers, wire-format triple-sync, and drift-gate discipline the repo already uses. Read existing specs, mirror the template, ship the protocol type + zod schema + JSON Schema in one pass.
Craft commit messages that match motebit's Conventional Commits + co-author + HEREDOC conventions. Read the diff, lead with the architectural why, never skip hooks.