Frontend Code ReviewCAUTION
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
Overview
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
298496c93d3dOBSERVED · 2026-10-21What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: frontend-code-review description: Use only when the user explicitly requests a review or audit of frontend code under `web/` or `packages/dify-ui/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, or backend-only code. --- # Frontend Code Review Review the requested scope for concrete defects and violations of explicit project contracts. This skill owns review decisions; its references route to canonical rules without activating another skill's implementation workflow. ## Evidence First 1. Establish the review scope from the requested files or current diff. 2. Read the changed lines, their behavior owner, and the nearest scoped `AGENTS.md`. 3. Trace public consumers, generated contracts, primitive APIs, or runtime configuration only when they decide correctness. 4. Report findings tied to an observable failure, violated contract, security boundary, or demonstrated maintenance risk. Explicit team conventions are contracts: establish their scope and exceptions, and do not invent user impact to justify a convention finding. ## Rule Routing Read only the packs matched by the diff: - DOM semantics, focus, keyboard, forms, disabled state, or visible interaction: [`references/accessibility-ui.md`][accessibility] - Dify UI imports, Base UI wrappers, overlays, tokens, or primitive contracts: [`references/dify-ui.md`][dify-ui] - Component ownership, props, state, Effects, navigation, or module boundaries: [`references/component-architecture.md`][component-architecture] - Generated clients, Query, mutations, auth, SSR, URL state, or persistence: [`references/data-query-contracts.md`][data-query] - Test files or a concrete missing-regression-test finding: [`references/testing.md`][testing] - Bundle, waterfall, rendering, or subscription cost supported by evidence: [`references/performance.md`][performance] - Stable Dify runtime invariants in the named paths: [`references/dify-invariants.md`][dify-invariants] - General TypeScript or styling quality not owned above: [`references/code-quality.md`][code-quality] Read `packages/dify-ui/README.md`, `packages/dify-ui/AGENTS.md`, `packages/dify-ui/docs/overlays.md`, or `web/docs/test.md` only when the reviewed code falls under that contract. Check current official documentation when local code and bundled references do not settle a framework, browser, or accessibility behavior. ## Severity And Output - **P0**: security or privacy leak, data loss, production crash, or inaccessible critical workflow. - **P1**: user-visible regression, invalid API or authorization contract, hydration failure, or broken primary interaction. - **P2**: concrete maintainability, performance, test, or accessibility defect, or a material violation of an explicit project contract. - **P3**: minor actionable cleanup; omit unless the user requested a thorough audit. Lead with findings ordered by severity. Include a tight file and line reference, the observed failure or applicable project rule, and a concrete fix direction. Explain the rule's applicability for convention findings; describe downstream consequences only when supported by evidence. When no findings remain, say so briefly and state any material verification gap. Do not add praise sections, speculative risks, or an unsolicited offer to implement fixes. [accessibility]: references/accessibility-ui.md [code-quality]: references/code-quality.md [component-architecture]: references/component-architecture.md [data-query]: references/data-query-contracts.md [dify-invariants]: references/dify-invariants.md [dify-ui]: references/dify-ui.md [performance]: references/performance.md [testing]: references/testing.md
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (5)
.claude/skills/backend-code-review
.claude/skills/e2e-cucumber-playwright
.claude/skills/frontend-code-review
.claude/skills/frontend-testing
.claude/skills/how-to-write-component
Gates applied: no_behavioural_pass.
298496c93d3dfull audit observations/trust-audit/skill/langgenius__frontend-code-review.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-21 | 298496c93d3d | CAUTION | B | 89 | first audit |
Questions
What does the frontend-code-review — langgenius/dify skill do?
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
Is frontend-code-review — langgenius/dify safe to install?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can frontend-code-review — langgenius/dify access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (298496c93d3d), read on 2026-10-21. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/langgenius/frontend-code-review/)
Not your listing, or something out of date? Claim or update your listing.