Run the technical (code) review step of Flows app certification. Produces three artifacts under reviews/code-review/feedback-round-<N>/: review-files.md (per-file inventory), review-packages.md (dependency audit), and code-review-report.md (scored report with Must Fix / Should Fix / Nice Fix items). 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
flows-code-review is the technical review stage of Cognite's Flows app certification pipeline. It exists to give a repeatable, evidence-backed gate between building a Flows (Node/TypeScript) app and submitting it for certification, so that reviewers do not have to reconstruct scoring criteria from memory each round. Running it produces three artifacts under reviews/code-review/feedback-round-<N>/: a per-file inventory (review-files.md), a dependency audit (review-packages.md), and a scored report (code-review-report.md) that classifies findings as Must Fix, Should Fix, or Nice Fix. The skill is designed to be re-run until zero open Must Fix items remain before moving on to the design review step.
Three markdown artifacts per feedback round: a per-file inventory scoring structure, quality, patterns and tests; a package audit of outdated and vulnerable dependencies; and a scored report grouping findings as Must Fix, Should Fix, and Nice Fix.
A Node/TypeScript project with a package.json inside a git repository. It also expects the companion Cognite review skills (security, test-coverage, code-quality, etc.) to be available locally, and warns if App-Brief.md is missing at the repo root.
It uses Read, Glob, Grep, Bash, and Write. Its Bash usage is limited to inspection commands like git rev-parse, npm outdated, npm audit, and the project's test suite with coverage (vitest/jest).
Yes. Overall line coverage must be at least 80% for the app to be approved, measured across production .ts/.tsx files under src/, and coverage exclusions that hide untested code are themselves treated as a finding.
When asked for a Flows code review, technical review, pre-submit review, or app certification code review. Re-run each round until no open Must Fix items remain, then proceed to flows-design-review.
Quick Setup:
.claude/skills/Repository
cognitedata/builder-skills