What problem does it solve? Pull requests often lose their link to the tracked task: the Closes #N line is missing, labels are guessed instead of read from the issue, and tasks stay open when a PR merges into an epic or chain branch instead of the default branch. This Skill defines the exact structure and commands for writing a PR body that keeps the board, the reviewer queue, and task closure in sync. ## Core Features & Use Cases - Mandatory task linking: Enforces the Closes #<number> line and explains how task closure works when the PR base is an epic branch or a chain branch rather than the main branch. - Reviewer, assignee, and label setup: Sets reviewer, assignee, and labels at PR creation via gh pr create, or on an already open PR via REST API calls when gh pr edit fails. - Four-section body template: Provides a fixed body structure — link line, what was done, what confirms it, and the remaining step — including how to rewrite the body after merges into the branch. - Use Case: When opening a PR against an epic branch, use this Skill to write a body that names how the task closes (via the tree's pipeline or manually) so the queue audit never flags the PR as divergent. ## Quick Start Ask the assistant to write the body for a pull request that closes issue #86, including the Closes line, the four required sections, and the correct reviewer, assignee, and labels.
