Backend Code Review

Review the requested scope for concrete, reproducible defects. The nearest AGENTS.md owns package facts and commands; this skill owns the review workflow and routes to its bundled rule packs.

Evidence First

1. Establish the requested review scope and inspect the relevant diff or files.
2. Read the changed lines, their behavior owner, nearby tests, and local docstrings or comments that define contracts.
3. Trace callers, persistence boundaries, authorization, generated schemas, or external I/O only when they decide correctness.
4. Report only findings tied to an observable failure, violated contract, security boundary, data integrity risk, or demonstrated maintenance problem.

Rule Routing

Read only the packs matched by the diff:

• Models or migrations: [references/db-schema-rule.md][db-schema]
• Controller, service, core/domain, library, or model dependency direction: [references/architecture-rule.md][architecture]
• Table access outside an established repository boundary: [references/repositories-rule.md][repositories]
• SQLAlchemy sessions, queries, transactions, CRUD, concurrency, or raw SQL: [references/sqlalchemy-rule.md][sqlalchemy]