Contextual Git Commit

Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.

The user will provide the commit headline as an argument (e.g. /chalk:commit fix: boolean logic error in expression.clj).

Before you draft

A commit body is an explanation artefact and MUST be drafted in the chalk voice, not your own default prose habits. chalk:commit pulls in nothing on its own, so load these first (via the Skill tool):

• chalk:voice — the principles, the explanation quadrant, the line-format rule.
• chalk:mindmap — a commit body is a lead-in line then a tree, not prose. See "Commit bodies" there.
• chalk:code-comments — the body is where a comment's design rationale belongs, so this is the moment the misfiled ones surface.

The body MUST NOT contain headings — needing them is a signal the commit is too big, or that you're writing the PR description in the wrong place. A tl;dr is optional; the subject line normally serves as one.

Your responsibilities