Pull Request

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

The user MAY provide a PR title as an argument (e.g., /chalk:pr feat: read-only secondaries). If no title is provided, draft one from the branch's commits.

Before you draft

A PR description is an explanation artefact, and it MUST be drafted against the chalk voice — not your own default prose habits, which read wrong and lose the reasoning the reviewer needs.

chalk:pr loads on its own and does not pull the shared voice into context. Before drafting the description, load the chalk:voice skill (via the Skill tool) — it carries the Diataxis framing, the universal principles, and the issue/PR section palette. Then structure the description into sections drawn from that palette, choosing the ones this change needs. A wall of undifferentiated prose is the wrong shape; if you've written one, you skipped this step.

Line format: paragraph-per-line. A PR description is read rendered on GitHub, never as a git diff. GitHub renders single newlines as <br>, so sentence-per-line fragments into staccato — put each paragraph on a single line, separate paragraphs with a blank line, and let the rendering wrap.