backend-review

Review Node.js, Java, and microservice code for security and correctness issues.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill backend-review-camilooscargbaptista
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-review
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/backend-review
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill backend-review-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill delivers deep, production-focused backend code reviews that find correctness, security, performance, and reliability issues that surface-level feedback misses, ensuring services are maintainable and safe to operate at scale.

Core Features & Use Cases

  • Comprehensive File-by-File Analysis: Systematic checks for correctness, error handling, edge cases, and maintainability across source files.
  • Endpoint and Database Review: Validates input validation, authentication/authorization, pagination, rate limiting, SQL indexes, N+1 patterns, and query timeouts.
  • Architecture, Messaging & Payments: Reviews Clean Architecture and SOLID compliance, idempotency for payment flows, messaging best practices (DLQs, schema versioning), and failure-mode scenarios (3am + traffic spikes).
  • Actionable Output: Produces prioritized findings, remediation steps, required tests/migration checks, and risk assessment to guide engineering teams.

Quick Start

Review the backend service in src/ for security, performance, database, and messaging issues and return a prioritized remediation plan.

Frequently Asked Questions about backend-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review backend code for security vulnerabilities and performance issues?

To review backend code for security and performance, perform a file-by-file analysis to identify input validation flaws, missing SQL indexes, N+1 query patterns, and authorization gaps, ensuring services are safe and maintainable at scale.

What is the best way to check for idempotency and failure modes in payment flow logic?

Checking payment logic for idempotency and failure modes involves analyzing transaction boundaries, retry strategies, and messaging schemas to ensure correctness during traffic spikes, providing remediation steps to prevent duplicate transactions.

Does this backend code review approach work with Node.js and Java microservices?

Yes, this backend code review approach works with Node.js and Java microservices, applying systematic checks for correctness, error handling, and architecture compliance to projects using Express, NestJS, Spring, or similar server-side frameworks.

How do I find N+1 query problems and missing database indexes in my server-side code?

To find N+1 query problems and missing database indexes, review server-side database queries and endpoint interactions, validating pagination, query timeouts, and transaction boundaries to produce a prioritized list of performance fixes.

Can I validate Clean Architecture and SOLID compliance in my microservice codebase?

Yes, you can validate Clean Architecture and SOLID compliance in a microservice codebase by reviewing messaging flows, schema versioning, and dead-letter queue configurations, receiving a risk assessment and required tests to guide engineering teams.

Why does my backend service fail during traffic spikes and how do I analyze failure modes?

Analyzing backend failure modes during traffic spikes requires checking timeout and retry strategies, transaction boundaries, and messaging configurations, producing a prioritized remediation plan to ensure reliability under high-load scenarios.