approve-review
Open a review-action approval window by creating the ./.review-approved flag file. Takes an optional reason string that is embedded in the receipt chain.
A command is the one you type. It runs exactly when you ask it to, and never before.
3,345 commands across 357 plugins.
Open a review-action approval window by creating the ./.review-approved flag file. Takes an optional reason string that is embedded in the receipt chain.
Walk the receipt chain in ./receipts/ verifying every signature and hash link. Detects insertions, deletions, and tampering across the entire audit trail.
Properly archive completed orchestrations while preserving valuable data, metrics, and lessons learned for future reference.
When user is asking for guidance for which role to assign to an identity given desired permissions, this agent helps them understand the role that will meet…
Implement blue-green deployment strategy with zero-downtime switching, health validation, and automatic rollback
Starte Manus-artige Dateiplanung. Erstelle task_plan.md, findings.md, progress.md für komplexe Aufgaben.
Self-check for the planning-with-files mechanisms that fail silently: plan resolution, hook injection, canonicalizer path shape, attestation state, install…
Iniciar planificación de archivos estilo Manus. Crear task_plan.md, findings.md, progress.md para tareas complejas.
Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
Stage working tree changes and create a Conventional Commit (no push).
Reverse-engineer a frontend codebase into a PRD. Usage: /code-to-prd [path]
Complete an epic after all tickets are executed, generate report, and close in Jira
Generate comprehensive sprint retrospective from completed epics
Complete a ticket after execution - transitions Jira to "In Review" and updates the implementation plan
Step 1 of the vibe-coding workflow: validate the app idea with deep research before anything gets built.
Step 3 of the vibe-coding workflow: plan HOW to build it — stack, architecture, costs, deployment.
The vibe-coding workflow turns an app idea into a working MVP in 5 stages. Your job: figure out where the user is and route them to the right stage.
Development practices and TDD workflow to follow before starting a feature
LLM unit testing best practices checklist for testing internal logic, not API endpoints
Run all Brooks-Lint analyses in one pass, auto-fix safe findings, confirm risky ones
Link your local development project to a hosted Supabase project.
Connect the Supabase CLI to your Supabase account by logging in with your [personal access token](https://supabase.com/dashboard/account/tokens).
Hit the Cloudflare REST API for bulk, fleet, and operations wrangler can't do
Scaffold and deploy a Cloudflare Worker with Hono routing
Compute the recent 7-day spend trend (burn rate) from daily sessions and per-session cost.
Compare two sessions side-by-side with cost and workflow deltas
Quick total cost plus a per-model one-liner from the dashboard pricing engine.
Stage working tree changes and create a Conventional Commit (no push).
**Easy wrapper for running Codex CLI commands from Claude Code with proper syntax.**
Stage, commit, and push the current branch following git governance rules.
Restart the reflexio backend and dashboard to pick up new changes
Show this project's saved Recall context (.recall/context.md)
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic