Loading...
Loading...
Found 5 Skills
Write a description to description GitHub Pull Request.
Writes the body of a pull request - the summary, the repository template sections, and reviewer guidance such as a recommended reading order and focus areas. Use whenever drafting or revising a PR description, filling in a repository's PR template, refreshing a description that no longer matches the branch, or preparing a branch for review. Use it even when the user only says "open a PR", "put this up for review", or "write this up" without naming the description.
Only use when the user explicitly invokes this skill by name.
Write a concise GitHub pull request body with five headings. The headings are Background, Design Decisions, Changes, Verification Performed, and Post-Merge Operations. When you create, open, submit, or update a pull request, use this skill. Use it for a PR description or for gh pr create. Do not use this skill for commit messages alone.
Write a branch's PR body that tells a reviewer how much attention it needs, with a visual summary, harvested evidence and a fresh-context one-way or two-way door call, then put it and an attention label on the branch's PR. Use when a branch is ready for review, when the user says "write the PR body", "update the PR description", "how risky is this PR", or "is this ready to merge", and when another skill closes a branch.