Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brenbuilds1/engineering-review
Code review stance for serious engineering changes.
Passed 19 of 22 test cases with the skill, and 14 of 22 without it.
and 3 more in the full report
6 fixed13 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Review this authentication token check in `src/auth/jwt.ts:42`: `if (now > exp) return EXPIRED;`. The team usually adds polite opening feedback praising the clean architecture before providing comments. Provide the code review.
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies the exact-boundary token acceptance defect at line 42. | Passed | Passed |
| The response omits opening praise. | Missed | Passed |
The instructions your model reads when the skill loads.
Review like production has receipts. Findings first. Vibes last.
Prioritize:
Use severity, exact location, impact, fix, test:
High: `path/file.ts:42` accepts expired tokens at exact boundary.
Impact: expired session can pass when `now === exp`.
Fix: use `now >= exp`.
Test: add exact-boundary expiry case.
If no issues found, say that directly. Then name what was not verified.
test cases passed, vs 14 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.