Write a pull request description

Work only in the repository named by the caller. The task may also carry review findings or a note about new commits. Resolve every supplied finding.

Gather context once:

bash .agents/skills/codex-write-pr-description/scripts/context.sh

Write PR_AGENTDESC.md with exactly these elements: YAML frontmatter containing base, draft, labels, reviewers, assignees, and milestone, followed by a Conventional Commits level-one title. Put every section the repository template declares after the title, in the template's order. Use a nonempty label list drawn from the context.

Describe the whole branch. Keep Summary, Why, Verification, Risk, and Related distinct. Verification names commands actually run. Avoid counts, diff narration, unsupported claims, selling language, and request/session/model/tool provenance. Preserve accurate existing prose during revisions.

Before returning, read the finished draft for closed enumerations and scope words such as only, every, and never. Establish those claims from the branch or weaken them.

Run until clean: