Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/Reviewing Code
Systematically evaluate code changes for security, correctness, performance, and spec alignment.
Passed 18 of 23 test cases with the skill, and 6 of 23 without it.
and 15 more in the full report
14 fixed4 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
At the end of a code review summary report, what are the three valid aggregate assessment ratings for deciding the fate of a pull request?
| Checked | Without skill | With skill |
|---|---|---|
| The valid assessment options include APPROVE. | Passed | Passed |
| The valid assessment options include NEEDS REVISION. | Missed | Passed |
The instructions your model reads when the skill loads.
Evaluate code changes across security, correctness, spec alignment, performance, and maintainability. Apply sequential or parallel review based on scope.
Sequential (small PRs, <5 files):
Parallel (large PRs, >5 files):
Read documentation:
docs/feature-spec/F-##-*.md — Technical design and requirementsdocs/user-stories/US-###-*.md — Acceptance criteriadocs/api-contracts.yaml — Expected API signaturesdocs/data-plan.md — Event tracking requirements (if applicable)docs/design-spec.md — UI/UX requirements (if applicable)docs/system-design.md — Architecture patterns (if available)docs/plans/<slug>/plan.md — Original implementation plan (if available)Determine scope:
Security (/25)
test cases passed, vs 6 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.