flows-app-review
Flows App 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-app-review/feedback-round-<N>/as the artifact directory for local reviews. - If no local feedback round exists yet, use
reviews/flows-app-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-app-review/feedback-round-<N>/instead ofreviews/<TICKET-ID>/feedback-round-N/. - Verify the review against the local source code before declaring it complete.
More from cognitedata/builder-skills
use-topbar
>-
60code-quality
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.
60skill-creator
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.
60integrate-todo-list
MUST be used whenever adding a task/todo list feature to a Flows app with Atlas chat. Do NOT manually create todo state management or tool definitions — this skill handles the full module (context, provider, tool, hooks, UI components) and all integration wiring. Prerequisite: integrate-atlas-chat must already be set up. Triggers: todo list, task list, task tracking, TodoWrite, todo panel, task panel, progress tracking, add todos, add tasks.
60correctness-and-error-handling
MUST be used whenever fixing correctness and error handling issues in a Flows app. This skill finds AND fixes bugs, missing error states, unhandled rejections, and edge-case failures — it does not just report them. Triggers: correctness, error handling, bug fix, edge case, crash, unhandled, null, undefined, empty state, loading state, error boundary, try catch, async error, useEffect cleanup, type guard, runtime error, robustness.
60security
MUST be used whenever fixing security issues in a Flows app, or before shipping any feature that handles credentials, user input, or external data. This skill finds AND fixes security problems — it does not just report them. Do NOT skip this when the user asks for a security fix, security hardening, or vulnerability remediation — run every step in order. Triggers: security, security fix, security hardening, vulnerability, XSS, injection, credentials, secrets, auth, authentication, authorization, token, sensitive data, input validation, CORS, CSP, dependency audit.
59