write-pr-description

# Write a pull request description Write `PR_AGENTDESC.md` at the repository root, then return. You run forked, so the branch diff sits in your context rather than the caller's. Read the material below and write from it. ## Arguments `$ARGUMENTS` carries the repository root, and after it whatever the caller wants addressed. A first draft arrives with nothing extra. A revision arrives carrying the findings `review-pr-description` returned, or a note that remediation added commits the description hasn't caught up with. Treat any findings in the arguments as the work. Resolve each one and say so. ## Context !`bash ${CLAUDE_SKILL_DIR}/scripts/context.sh` ## The shape Write the file in exactly this order. ```text --- base: <branch this merges into> draft: <true or false> labels: [<one or more from the set above>] reviewers: [] assignees: [] milestone: --- # <type>(<scope>)?: <description> ## <first template section> <prose> ``` Those frontmatter keys and no others. Labels take a flow sequence and an empty one fails the validator, because nobody's filter finds an unlabelled pull request. The title is a level 1 heading in the Conventional Commits shape. A squash merge turns it into the commit subject on the default branch, so its type has to be one the landing commits use, and it names what the whole branch does rather than what the last commit did. Then every section the template declares, in the template's order, filled with prose. Replace each instructional comment...