backend-code-review
Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, frontend code, or backend code outside `api/`.
Profile →npx skills add langgenius/dify --skill backend-code-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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] When n
- Evidence First
- Rule Routing
- Severity And Output
What does the backend-code-review skill do?
Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, frontend code, or backend code outside `api/`.
How do I install it?
Run `npx skills add langgenius/dify --skill backend-code-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From langgenius/dify, a repository with 151,326 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.