legion-pr-write

Load the criteria with legion issue view, re-read your diff with git diff main..HEAD, then write one ### subheading entry per criterion containing explanatory prose and a line of evidence such as a test name or file:line. Validate the result with legion pr write-check before opening the PR.

The parser splits mapping entries on ### subheadings only; bullets, numbered lists, and bold headings are invisible to it, and everything before the first ### is discarded. A body with five bullets and three ### headings counts as three entries.

The mapping section heading must contain both the words acceptance and mapping, and issue criteria are read only from ## headings exactly matching Acceptance criteria, Acceptance, Done when, or Done with no trailing punctuation. Fix the heading rather than rewriting the body.

Yes, passing --closes <issue> appends a Closes #<issue> line idempotently, and it is repeatable for multiple issues including cross-repo owner/repo#N references. GitHub requires the keyword before each reference, so repeatable --closes emits one line per issue.

The recorded gate no longer matches HEAD, so you must re-run legion pr write-check on the updated body. Re-running overwrites the previous gate row for HEAD, and the most recent result wins.