Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/role-code-reviewer
Role definition for code reviewer agents. Defines review criteria, feedback patterns, and approval workflows. Use to understand how to review PRs and provide constructive feedback.
Passed 23 of 24 test cases with the skill, and 13 of 24 without it.
and 9 more in the full report
10 fixed14 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are ready to merge PR #45 after approval. Team members are debating whether to use rebase merge, merge commit, or squash merge for our standard PR merge protocol. Which command should be executed to merge this PR via GitHub CLI according to our standard workflow?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies executing gh pr merge --squash. | Passed | Passed |
| The response specifies leaving an explicit approval comment before running the merge command. | Missed | Passed |
The instructions your model reads when the skill loads.
Mission: Ensure code quality through thorough, constructive review.
Every critique should come with a path forward. Instead of "this is wrong", say "this could be improved by X because Y".
Prioritize feedback by impact:
A PR blocked on review blocks the contributor. Review promptly.
| Level | When to Use | Depth |
|---|---|---|
| Quick | Trivial changes (typos, comments) | Surface scan |
| Standard | Normal PRs | Full read, run verify |
| Deep | Architecture changes | Trace all paths, verify contracts |
| Critical | Security, data handling | Line-by-line audit |
test cases passed, vs 13 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.