flows-code-review
Run the technical (code) review step of Flows app certification in a local git app. Loads flows-review-checks for the actual bar, then writes artifacts under reviews/code-review/feedback-round- /. Use when the user asks for a Flows code review, technical review, pre-submit review, app certification code review, or "run flows-code-review". Re-run until 0 open Must Fix items remain before moving on to flows-design-review.
- Installs
- 1.6K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/cognitedata/builder-skills --skill flows-code-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads flows-code-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Flows Code Review
This skill is the local runner for the technical review step:
flows-app-brief → build → flows-code-review (this skill, repeat until clean) → flows-design-review → flows-external-app-submit
Checks and scoring live in flows-review-checks. Do not copy them here. Do not score from memory. Do not substitute test-coverage or other fix skills for the review bar.
This file only decides: git/app-brief pre-checks, feedback-round folder, that the working directory is the app root, where to write files, and the submitter Summary block.
Pre-checks
package.jsonexists- We are inside a git repository (
git rev-parse --git-dir) - If
App-Brief.mdis missing at repo root, warn thatflows-app-briefshould be run first, but continue
Feedback round: look at reviews/code-review/. If it doesn't exist, use feedback-round-1/. Otherwise the next missing round number.
Working directory for all review commands: repo root (the app).
Step 1 — Pull latest checks from cognitedata/builder-skills, then run them
Every review run must start by taking flows-review-checks and code-quality from cognitedata/builder-skills. Do not score from whatever is already in the app’s skills/ folder.
If this workspace already is builder-skills (git remote contains cognitedata/builder-skills): you are in that repo — Read local skills/flows-review-checks/SKILL.md (it loads local code-quality).
Otherwise (reviewing an app): pull those two skills from this repo, then read them:
npx @cognite/cli@latest apps skills pull --skill flows-review-checks
npx @cognite/cli@latest apps skills pull --skill code-quality
If the CLI pull fails, get the same two files from main:
curl -fsSL https://raw.githubusercontent.com/cognitedata/builder-skills/main/skills/flows-review-checks/SKILL.md
curl -fsSL https://raw.githubusercontent.com/cognitedata/builder-skills/main/skills/code-quality/SKILL.md
Then Glob '**/skills/flows-review-checks/SKILL.md' and Read the first match (after a successful pull, that is the copy you just fetched). Follow it completely: hunt (including code-quality searches — do not apply its fixes), packages, coverage, scores, categorization, shared verify.
Step 2 — Write artifacts here
Round dir: reviews/code-review/feedback-round-<N>/
| Shared output | Filename here |
|---|---|
| File inventory | review-files.md |
| Hunt + must/should/nice | review-findings.md |
| Package audit | review-packages.md |
| Scored report | code-review-report.md |
code-review-report.md must include everything flows-review-checks requires (checks performed, coverage scope, scores 1.1 and 1.3–1.6, 2.1–2.6, 3.1, must/should/nice with _Impact:_ on Must Fix), plus:
# [App name] — Flows code review
This document is the platform review for [App name], conducted as part of the Cognite Flows app certification process.
## Path to approval
This review found **[N] must-fix item(s)** that block approval. Once the must-fix items are addressed, re-run `flows-code-review`.
### Reviewed commit
`<full SHA>`
End code-review-report.md with this block (required by flows-external-app-submit):
## Summary
- Must Fix open: <integer>
- Should Fix open: <integer>
- Nice Fix open: <integer>
Use exactly those labels. When all Must Fix items are resolved: Must Fix open: 0.
Step 3 — Runner verify
After flows-review-checks Step 6:
- The four files above exist in this round’s folder.
- This run pulled (or, in
builder-skills, already had) currentflows-review-checksandcode-qualityfromcognitedata/builder-skillsbefore scoring. - Print:
Must Fix open: <n>
Should Fix open: <n>
Nice Fix open: <n>
When to stop
Re-run this skill until Must Fix open: 0 in the latest round’s code-review-report.md. Only then proceed to flows-design-review.
FAQ
What does the flows-code-review skill do?
Run the technical (code) review step of Flows app certification in a local git app. Loads flows-review-checks for the actual bar, then writes artifacts under reviews/code-review/feedback-round- /. Use when the user asks for a Flows code review, technical review, pre-submit review, app certification code review, or "run flows-code-review". Re-run until 0 open Must Fix items remain before moving on to flows-design-review.
How do I install flows-code-review?
Run npx skills add https://github.com/cognitedata/builder-skills --skill flows-code-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/flows-code-review/ (personal) or .claude/skills/flows-code-review/ (project).
Which AI agents can use flows-code-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is flows-code-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains flows-code-review?
It is published by cognitedata in cognitedata/builder-skills. It has 1,586 recorded installs.
More from cognitedata/builder-skills
skill-creator
cognitedata/builder-skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch for Claude Code or Cursor, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
code-quality
cognitedata/builder-skills
MUST be used whenever reviewing a Flows app for code quality, maintainability, or clean code issues — before a PR review, after a feature is complete, or when the user asks for a code review. Do NOT skip linting steps. Triggers: code quality, code review, clean code, refactor, maintainability, technical debt, any type, naming, dead code, duplication, DRY, single responsibility, component size, lint, linting, TypeScript strict, dependency injection, file structure.
test-coverage
cognitedata/builder-skills
MUST be used whenever fixing test coverage for a Flows app to meet the 80% line coverage hard gate. This skill finds AND fixes coverage gaps — it configures tooling, writes missing tests, covers untested paths, and refactors code for testability. It does not just report. Triggers: test coverage, fix tests, write tests, add tests, coverage fix, 80% coverage, coverage gate, missing tests, testability, vitest coverage, jest coverage.
dependencies-audit
cognitedata/builder-skills
MUST be used whenever fixing dependency issues in a Flows app. This skill finds AND fixes vulnerabilities, outdated packages, deprecated dependencies, and license issues — it does not just report them. Triggers: dependencies, packages, fix dependencies, update packages, fix vulnerabilities, npm audit fix, pnpm audit fix, CVE fix, outdated, deprecated, supply chain, license.
design
cognitedata/builder-skills
Simplified Aura guidance for selecting primitives, keeping token usage consistent, and applying reliable layout/copy/state patterns in Flows and Fusion apps.
reveal-3d
cognitedata/builder-skills
Integrates the @cognite/reveal-widget npm package into Flows apps for an interactive Cognite Reveal 3D Scene/CAD/point cloud/360-image viewer. Use when adding 3D viewer, 3D visualization, Reveal, CAD model, Point cloud model, 360 image collection, Scenes, RevealWidget, RevealWidgetController, DM 3D mapping, asset 3D model, model browser, or Cognite 3D content to a Flows application.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.