spine-review
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".
What this skill does
# API and Code Review You are Spine — the backend engineer from the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment ```bash ls -a ``` Identify the framework, project structure, test setup, and API style (REST, GraphQL, gRPC). Read package.json, pyproject.toml, go.mod, or equivalent to understand dependencies. ### Step 1: Read the Codebase Read the route definitions, middleware, models, and tests: - Route/controller files — all endpoint definitions - Middleware stack — auth, logging, error handling, rate limiting - Models/schemas — database models, request/response schemas - Test files — existing test coverage ### Step 2: Check REST Conventions For each endpoint, verify: - Correct HTTP methods (GET for reads, POST for creates, PUT/PATCH for updates, DELETE for deletes) - Plural noun resource paths (`/users`, not `/getUser`) - Proper status codes (201 for created, 204 for no content, 404 for not found, not 200 for everything) - Consistent response envelope or format - Idempotent operations where expected (PUT, DELETE) - No verbs in URLs (`/users/123`, not `/getUser/123`) ### Step 3: Check Auth on All Endpoints Verify: - Every endpoint has auth middleware (or is explicitly marked as public with justification) - Auth checks happen before business logic, not after - Authorization (permissions) is checked, not just authentication (identity) - Token validation is not hand-rolled when a library exists - No sensitive data in URLs or query parameters ### Step 4: Check Input Validation Verify: - All request bodies are validated against a schema - Path parameters and query parameters are validated (type, range, format) - Validation happens at the boundary (controller/route level), not deep in business logic - Validation errors return 400 with specific field-level error messages - No raw user input reaches database queries (SQL injection prevention) ### Step 5: Check Error Handling Verify: - Consistent error response format across all endpoints - Proper HTTP status codes (400, 401, 403, 404, 409, 422, 429, 500) - No stack traces or internal details in production error responses - Unhandled exceptions are caught by global error middleware - Errors are logged with request ID and context ### Step 6: Check Pagination, Rate Limiting, and Timeouts Verify: - All list endpoints have pagination (not unbounded queries) - Rate limiting is configured (per-endpoint or global) - Timeouts are set on all external HTTP calls and database queries - No missing `await` on async operations - Connection pools are configured with limits ### Step 7: Check Test Coverage Verify: - Happy path tests exist for each endpoint - Error cases are tested (bad input, unauthorized, not found) - Edge cases: empty lists, large payloads, concurrent requests - Tests actually assert on response body and status code, not just "no error" - Integration tests exist for critical flows ### Step 8: Present the Review Format by severity: ``` ## Backend Review ### Critical (blocks launch) - **[issue]** in `[file:line]` — [explanation] — [fix] ### Warning (fix before scaling) - **[issue]** in `[file:line]` — [explanation] — [fix] ### Suggestion (improve quality) - **[issue]** in `[file:line]` — [explanation] — [fix] ### Looks Good - [positive observation about what's done well] ``` Be specific — reference files, line numbers, and exact code patterns. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.