Backend code review for Dify's api: evidence-first findings with a severity ladder
Evidence-first backend reviews — inspect the diff, route to rule packs (DB schema, architecture, repositories, SQLAlchemy), report P0–P3 findings tied to observable failures
- What
- Evidence-first backend reviews — inspect the diff, route to rule packs (DB schema, architecture, repositories, SQLAlchemy), report P0–P3 findings tied to observable failures
- Cost
- Free
- Needs
- a backend change to review (best suited to Dify's own api/ layout, since the rule packs are Dify-specific) — the skill is a review methodology, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @langgenius's backend code review skill, written for the Dify project's own backend (reviews target code under `api/`). The discipline: evidence first — inspect the requested diff or files, read the changed lines plus their behavior owners and nearby tests, trace callers and boundaries only where they decide correctness, and report ONLY findings tied to an observable failure, violated contract, security boundary, data-integrity risk, or demonstrated maintenance problem. Reviews route to bundled rule packs read by diff type: DB schema, architecture, repositories, and SQLAlchemy; when no pack applies, correctness/security/behavior are reviewed directly against local contracts. Findings come on a severity ladder (P0 security/data-loss/outage, P1 user-visible regression or broken auth, P2 concrete correctness defect, P3 minor cleanup only on explicit request), ordered by severity with file:line references, failing contracts and fix directions — no praise sections, no speculative risks. Honest caveats: written for Dify's own repo layout (the `api/` scope and bundled rule packs are Dify-specific) — less useful as a generic reviewer; license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Backend code review for Dify's api is a free Muse skill for evidence-first backend reviews of Dify's backend code. The discipline is simple: inspect the requested diff or files first, then route findings to rule packs covering database schema, architecture, repositories and SQLAlchemy. Findings are reported on a P0 to P3 severity ladder, each tied to an observable failure.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it📌 Pinned version: commit 1a817b9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a backend change to review (best suited to Dify's own api/ layout, since the rule packs are Dify-specific) — the skill is a review methodology, not software Install "Backend code review for Dify's api: evidence-first findings with a severity ladder" for me. It gives my agent @langgenius's review workflow: establish scope and inspect the diff, read changed lines with their behavior owners and nearby tests, route to the matching rule packs (DB schema, architecture, repositories, SQLAlchemy), and report only evidence-backed findings on the P0–P3 severity ladder — no praise, no speculation. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://raw.githubusercontent.com/langgenius/dify/1a817b99720bd709d82a0084d73a7b44548cfbf8/.agents/skills/backend-code-review/SKILL.md Pinned version: install the code at commit 1a817b99720bd709d82a0084d73a7b44548cfbf8 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "backend-code-review". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. hand the agent the diff or files to review; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 1a817b9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox and failed · Nov 18, 2026 — Needs pnpm, npm cannot install it
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.