ReddRadar
Topic: code-review
652 skills in this topic.
-
flow-next-opencode-interview
Interview user in-depth about an epic, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1, fn-1.2) or file paths.
gmickel/flow-next-opencode 34
-
flow-next-opencode-ralph-init
Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
gmickel/flow-next-opencode 34
-
flow-next-opencode-export-context
Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.
gmickel/flow-next-opencode 34
-
flow-next-opencode-plan-review
Carmack-level plan review via RepoPrompt or OpenCode. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
gmickel/flow-next-opencode 34
-
flow-next-opencode-plan
Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1, fn-1.2).
gmickel/flow-next-opencode 34
-
flow-next-opencode-sync
Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
gmickel/flow-next-opencode 34
-
flow-next-export-context
Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.
gmickel/flow-next 567
-
flow-next-rp-explorer
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
gmickel/flow-next 567
-
flow-plan-review
Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.
gmickel/flow-next 567
-
flow-next-ralph-init
Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
gmickel/flow-next 567
-
flow-next-epic-review
Epic completion review - verifies all epic tasks implement spec requirements. Triggers on /flow-next:epic-review.
gmickel/flow-next 567
-
flow-next-setup
Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.
gmickel/flow-next 567
-
flow-next-setup
Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.
gmickel/flow-next 567
-
flow-next-deps
Show epic dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should epics run', 'critical path', 'which epics can run in parallel'.
gmickel/flow-next 567
-
flow-interview
Interview user in-depth about a spec, bead, or feature idea to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, discuss technical details, clarify a feature before building, or asks to be interviewed about their idea. Triggers on "interview me", "ask me questions about", "flesh out this spec", "refine requirements", "help me think through".
gmickel/flow-next 567
-
flow-next-prime
Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.
gmickel/flow-next 567
-
flow-next-deps
Show epic dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should epics run', 'critical path', 'which epics can run in parallel'.
gmickel/flow-next 567
-
flow-next-epic-review
Epic completion review - verifies all epic tasks implement spec requirements. Triggers on /flow-next:epic-review.
gmickel/flow-next 567
-
flow-plan
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).
gmickel/flow-next 567
-
flow-next-rp-explorer
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
gmickel/flow-next 567
-
flow-next
Manage .flow/ tasks and epics. Triggers: 'show me my tasks', 'list epics', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.
gmickel/flow-next 567
-
flow-next-export-context
Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.
gmickel/flow-next 567
-
flow-next-prime
Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.
gmickel/flow-next 567
-
flow-next-ralph-init
Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
gmickel/flow-next 567