Review TypeScript, Fastify, API, persistence, or server configuration changes for correctness, security, contract stability, data integrity, and verification gaps.
NewMaintained
Automatic
◆Coding pack
Last verified 8/28/2026
What it changes
Passed 3 of 10 test cases with the skill, and 8 of 10 without it.
Without skill82%
With skill27%
Checks it passed that the model alone missed
Omits formatting and quotation style preferences from findings
1 fixed5 passed either way3 still failing13 broke
Pass-rate lift
-55 pp
Tokens
+14%
Agent turns
0%
Response time
+25%
Model gemini-3.6-flashMeasured 8/28/2026v16 of 22 cases passed with skill · 10 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
Review `server/utils/formatter.js` where double quotes are used instead of single quotes and line indentation uses 4 spaces instead of 2.
What was checked, without and with the skill
Checked
Without skill
With skill
Omits formatting and quotation style preferences from findings
Missed
Passed
case-11 · gemini-3.6-flash · 8/28/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md26 linessingle file
Backend Code Review
Review only the requested files or current backend changes.
Required Context
Read the root and server package instructions.
Inspect the diff and the callers, routes, schemas, and persistence owners around each change.
Load the backend API checklist when validation, errors, configuration, or contracts are affected.
Review Priorities
Correctness, regressions, and error-path behavior.
Authentication, authorization, input validation, and secret exposure.
API and schema compatibility.
Transaction, idempotency, concurrency, and data-integrity risks.
Resource use, dependency readiness, and operational failure modes.
Missing behavior-level verification.
Output
Findings first, ordered by severity.
Include file and tight line ranges.
Explain the failure mode and a concrete fix direction.
Do not report style preferences as defects.
If no actionable findings exist, say so and list remaining verification risk.