Backend Slop Audit

A narrow, opinionated post-generation lint for backend/server-side code. Audits a changeset against a named catalogue of backend anti-patterns — swallowed errors, unvalidated input, missing timeouts, read-check-write races, N+1 queries, wrong status codes, unparameterized queries, hardcoded secrets, dead/duplicate handlers, and more — and returns specific, evidence-backed findings with the fix, not vibes. Use this whenever backend code was just written, generated, or pasted (an API route, service, handler, job, query, migration), when reviewing a server-side diff or PR, or when the user says "audit this backend", "does this look AI-generated / sloppy", "lint the server code", "review this endpoint/service/query", "any obvious backend mistakes here", or "is my error handling / validation / query OK". Reach for it proactively after generating any non-trivial backend code, even when the user didn't say the word "audit" — it's the server-side counterpart to ai-slop-audit (which lints frontend output). It is read-only: it finds and proposes; route accepted fixes to /refactor or the relevant specialist skill. Not for full security or performance audits (it defers those), pure frontend code, or subjective style.

mkdir -p ~/.claude/skills/backend-slop-audit
curl -L https://claudskills.com/skills/backend-slop-audit/SKILL.md \
  -o ~/.claude/skills/backend-slop-audit/SKILL.md

@misc{backend-slop-audit-2026,
  author    = {LucasSantana-Dev},
  title     = {Backend Slop Audit [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/backend-slop-audit/}
}