1.9 KiB
1.9 KiB
name, description, allowed-tools
| name | description | allowed-tools |
|---|---|---|
| flows-code-review | Run a full Flows app platform review against a React/TypeScript CDF codebase, following the cognitedata/dune-app-reviews scoring criteria. Produces three artifacts: review-files.md (per-file inventory), review-packages.md (dependency audit), and review-report.md (scored report with must/should/nice-fix items). Use when the user asks for a Flows app review, pre-submit review, approval review, app certification review, code quality audit, CDF platform review, or "run dune-review" on a codebase before submission. | Read, Glob, Grep, Shell, Write |
Flows Code Review
Fetch the official review command and follow it exactly:
gh api repos/cognitedata/dune-app-reviews/contents/.claude/commands/dune-review.md \
--jq '.content' | base64 -d
Adapt it for a local developer review:
- Treat the current workspace as the app under review.
- Skip all ticket, PR, overview, submodule, and
reviews/<TICKET-ID>/...setup steps. - If the upstream command asks for Jira ticket or PR input, ignore that requirement and continue with the local codebase.
- Use
reviews/flows-code-review/feedback-round-<N>/as the artifact directory for local reviews. - If no local feedback round exists yet, use
reviews/flows-code-review/feedback-round-1/. For reruns, increment the round number.
After the review artifacts are written, fetch the official verification command and follow it too:
gh api repos/cognitedata/dune-app-reviews/contents/.claude/commands/dune-review-verify.md \
--jq '.content' | base64 -d
Adapt verification the same way:
- Skip ticket and feedback-round lookup.
- Read the three artifacts from
reviews/flows-code-review/feedback-round-<N>/instead ofreviews/<TICKET-ID>/feedback-round-N/. - Verify the review against the local source code before declaring it complete.