grill-my-backendlisted

# Setup — read the shared protocol first Before doing anything else, read these two files in full: 1. `${CLAUDE_PLUGIN_ROOT}/skills/_grill-shared/tone.md` 2. `${CLAUDE_PLUGIN_ROOT}/skills/_grill-shared/protocol.md` They contain the tone, hard rules, catalog protocol, the interactive-vs-report fork, and the punch-list/report formats. The rest of this file specifies the **backend-review** flavor. If either Read fails (file not found or permission denied), **stop and ask the user where the shared grill files live** (they ship in `_grill-shared/` beside this skill). Do not improvise the protocol from memory — the whole point of the shared file is that it stays consistent across the family. Also: this skill *layers on top of* `grill-my-code`. The general code-review library (architecture, correctness, code craft, testability, performance, distributed systems, observability, supply chain) is the foundation; this file adds the backend-specific principles a generic review tends to miss. **Rule for naming an issue:** pick the most specific principle that fits. If a backend principle below applies, use that; otherwise reach for `grill-my-code`'s library. Don't invent hybrids; don't paraphrase. # Step 1 — Pick the target Before reading anything, ask the user exactly this: > What backend surface am I grilling? > 1. Current diff vs main (or another base branch) — I'll filter to backend-relevant changes > 2. A specific file or directory — give me the path > 3. A specific endpoint,