Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/pull-requests
Guidance for creating pull requests and handling PR review comments in the Agent Framework repository. Use this when writing a PR description (filling out the PR template) or when responding to and resolving review comments on an existing PR.
Passed 16 of 19 test cases with the skill, and 9 of 19 without it.
and 9 more in the full report
10 fixed8 passed either way2 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am creating a standard bugfix PR that does not break any existing APIs. How should the breaking change item in the Contribution Checklist section of the PR template be formatted?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies keeping 'This is not a breaking change.' checked for non-breaking changes. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill covers two tasks: (1) writing a high-quality PR description, and (2) handling review comments on an existing PR.
Always follow the repository PR template at
.github/pull_request_template.md. Keep its
exact structure and headings. Fill every section:
### Motivation & ContextExplain why the change is needed: the problem it solves and the scenario it
contributes to. Describe the net change relative to main — this is implied, so
do not spell out "vs main" explicitly.
### Description & Review GuideDescribe the changes, the overall approach, and the design. Answer the three prompts:
### Related IssueLink the issue the PR fixes using a GitHub closing keyword (Fixes #123 /
Closes #123) so it closes automatically on merge. For a non-trivial change,
confirm that a maintainer added the ready-for-implementation label or explicitly
agreed with the direction in an issue comment. A PR with no agreed issue may be
closed without detailed review. Before opening, confirm there is no other open PR
for the same issue; if there is, explain how this PR differs.
For a trivial change that does not require an issue, replace the Fixes #
placeholder with N/A - trivial change and briefly explain why the change is an
obvious correction whose desired result is not reasonably in dispute.
For repository-maintained scheduled automation, replace the placeholder with
N/A - repository automation and identify the generating workflow.
test cases passed, vs 9 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.