360-backend-auditlisted
Install: claude install-skill shahabahreini/360-skills
# 360 Backend Audit
## Purpose
Run this skill on **backend code**: APIs, services, business logic, data access layers, integrations, background jobs, and pipelines. Its job: turn working backend code into correct, lean, modular, observable, and transferable code, without breaking what already works.
This skill is technology-agnostic. It audits logic, structure, and data flow, not the syntax of any specific stack. UI and presentation concerns are out of scope.
## When to Use
- Before or after merging significant backend work
- When inheriting, refactoring, or modernizing services or data layers
- When code feels heavy, fragile, slow, or hard to debug in production
- Before handing code to another engineer or AI agent
## Core Principle
Working backend code is not finished code. Audit from every angle: what exists that shouldn't, what exists twice, what is subtly wrong, what runs slower than it should, what can't be diagnosed when it fails, and what the next engineer needs to continue safely.
One rule overrides everything: **functionality, reliability, and accuracy are untouchable.** A fast bug is still a bug. Every improvement must preserve all three, or be flagged as an explicit trade-off for the user to decide.
## Workflow
### 1. Map Before You Cut
Before changing anything, establish:
- What the code actually does: purpose, inputs, outputs, side effects
- Who calls it (endpoints, jobs, consumers) and what it depends on
- Where state is written, read, and transform