AGENT
Use when designing a new HTTP/GraphQL API or changing an existing one — modeling resources, defining endpoint contracts, choosing status codes, pagination,…
Copy-paste templates for leaving review comments. Keep each comment to one finding: an anchor, the problem, and the fix.
$ npx -y skills add vanara-agents/skills --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Copy-paste templates for leaving review comments. Keep each comment to one finding: an anchor, the problem, and the fix.
Copy-paste templates for leaving review comments. Keep each comment to one finding: an anchor, the problem, and the fix.
**[HIGH]** `path/to/file.js:88`
User-supplied `sort` is interpolated into the SQL string, allowing injection.
**Fix:** whitelist the sortable columns and bind the value:
\`\`\`js
const SORTABLE = { date: 'created_at', total: 'amount' };
const col = SORTABLE[sort] ?? 'created_at';
\`\`\`## Review summary - **Verdict:** Request-changes - **Blocking:** 1 HIGH (SQL injection at `repo.js:88`) - **Non-blocking:** 2 MEDIUM, 1 LOW Logic is sound and the tests are well structured. The one blocker is the dynamic sort column — once that's whitelisted this is good to merge. Detailed findings are inline.
## Review summary **Verdict: Approve** — read the full diff. Security, correctness, and tests all check out; no findings above LOW. Nice, focused change.
Prefix optional comments with `nit:` so authors know they don't block:
nit: `const d` → `createdAt` reads more clearly here.
🐒 Free agents, skills & packs for Claude Code One subscription. An army of Claude Code agents. 30 production-grade agents, skills, and packs for Claude Code — free, Apache-2.0, install with one command.
Repo: vanara-agents/skills
Use when designing a new HTTP/GraphQL API or changing an existing one — modeling resources, defining endpoint contracts, choosing status codes, pagination,…
This shows how the api-designer agent reviews a flawed draft. Findings are severity-ranked so the implementer fixes the contract-breakers first. Severity…
The contract is the deliverable. Express it as an **OpenAPI 3.1** document so it is human-readable *and* machine-checkable. This reference covers how to…
Run through this before declaring an API contract done. It is ordered the way you should *design*: resources first, cross-cutting rules last. Every box is a…
APIs are forever once published: a consumer you've never met may depend on any field you expose. Design so you can **add without breaking**, and version…
A complete review of a hypothetical PR, in the standard format. Use this as the model for tone, structure, and the anchor → problem → fix pattern.