backend-systems-auditor

Audits backend services and APIs against production engineering standards for idempotency, observability, and migrations.

1|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/sabiscore/swarmxq --skill backend-systems-auditor-sabiscore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-systems-auditor
Source: https://github.com/sabiscore/swarmxq/tree/main/.ai/skills/backend-systems-auditor
Command: npx skills add https://github.com/sabiscore/swarmxq --skill backend-systems-auditor-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backend services often ship with hidden production risks: missing idempotency keys, absent graceful shutdown handlers, unsafe database migrations, and no observability. This Skill systematically audits backend code, API designs, and migration strategies against production-grade engineering standards, producing specific findings with quantified risks and corrected code. ## Core Features & Use Cases - Six-Dimension Audit: Checks idempotency contracts, observability (traces/metrics/logs), graceful shutdown sequences, expand-migrate-contract migration discipline, API design correctness, and reliability/scalability patterns. - Prioritized Audit Report: Produces findings tiered as Critical, Important, and Improvements, plus numeric scores for observability, idempotency, and shutdown safety. - Corrected Code & Migration Review: Generates fixed implementations with inline before/after comments and a full migration safety analysis including lock duration and rollback strategy. - Use Case: Before deploying a Fastify service, paste your route handlers and Prisma migration files to receive a report flagging a missing SIGTERM drain handler, an N+1 query, and a NOT NULL column added without a default, each with a concrete fix. ## Quick Start Ask the assistant to audit your backend service code or migration files for production readiness using the backend systems auditor.

Frequently Asked Questions about backend-systems-auditor

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

FAQPage Schema
How do I audit my backend API for production readiness?

Submit your service code, route files, or schema migrations for a structured audit across six dimensions: idempotency, observability, graceful shutdown, migration discipline, API design, and reliability. The output is a prioritized report with critical findings, fixes, and numeric scores.

How to check if a database migration is safe to deploy?

A safe migration follows the expand-migrate-contract pattern: add nullable columns first, backfill data, then remove old structures in a later deploy. The audit flags NOT NULL columns without defaults, single-step renames, and full-table locks, and provides lock duration estimates and rollback strategy.

Does the audit work with Fastify, Express, and Prisma code?

Yes, the audit accepts Fastify, Express, and Hono route files, Node and Python services, and Prisma schemas and migrations. It checks framework-agnostic concerns like SIGTERM handlers, connection pool draining, N+1 queries, and idempotency keys on write endpoints.

What does a correct graceful shutdown sequence look like in Node?

On SIGTERM, stop accepting new requests, drain in-flight requests, finish active queue jobs, close the database pool, flush telemetry, then exit. The audit verifies each step, including Kubernetes preStop hooks and terminationGracePeriodSeconds configuration.

Why is idempotency important for POST and payment endpoints?

Without idempotency keys, retries can produce duplicate charges or records. The audit checks that write endpoints honor idempotency keys, use upserts instead of blind inserts, and that queue processors deduplicate before executing side effects.