Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Passed 11 of 17 test cases with the skill, and 6 of 17 without it.
and 9 more in the full report
8 fixed6 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am on a git branch and need to fetch PR comments, but I don't know the PR number. What official GitHub CLI command extracts just the PR number for the current branch in JSON format?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the command gh pr view --json number -q .number. | Missed | Passed |
The instructions your model reads when the skill loads.
Code review requires technical evaluation, not emotional performance.
Core principle: Fetch feedback → Verify → Implement → Re-test → Push updates.
Announce at start: "I'm using the Nori Receiving Code Review skill to handle this feedback."
For multi-item feedback, use TodoWrite:
- [ ] Fetch and read all PR comments
- [ ] Clarify unclear items (if any)
- [ ] Fix item 1: [description]
- [ ] Fix item 2: [description]
...
- [ ] Run tests/lint/format
- [ ] Push updates
Why: Prevents skipping items and provides visibility to user.
Determine PR number from context:
gh pr view --json number -q .numberFetch all comments:
# View all comments (review + general)
gh pr view [PR-NUMBER] --comments
test cases passed, vs 6 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.