recovery-diagnose
Automatic domain diagnosis: Core Update impact, VI drop, keyword losses, backlink profile.
A command is the one you type. It runs exactly when you ask it to, and never before.
9,228 commands across 665 plugins.
Automatic domain diagnosis: Core Update impact, VI drop, keyword losses, backlink profile.
Verify an implementation against the CCF spec — conformance, coding conventions, SOLID/OOP, and BE↔FE cross-check. Read-only review.
Execute the entire todo/in-progress backlog sequentially in this session, then run /ccf:check once and /ccf:updatespec.
Bootstrap a new project or onboard an existing one into the CCF workflow — generate CLAUDE.md + .claude specs + an initial sequential plan.
Full security audit of a Solidity/Vyper/Rust contract or directory. Runs the entire vuln-skills library and dispatches DeFi specialist subagents based on…
Audit only the git diff vs main (or specified base). Optimized for PR review.
Deep audit — same as /audit but spawns more parallel subagents, runs multi-pass review, and chases exploit chains across files.
Plan N days of binary outcomes (3 max/day), apply prompting principles, output branded HTML tracker
Interactive ritual to discover what "done" actually means for you. Run once. Produces your personal Define Done config.
5pm ritual. Check today's outcomes, log what shipped, flag what slipped, write tomorrow's 3.
Export this session's conversation to a markdown file
Analyzes a Chili Piper distribution (round-robin queue) for imbalance vs. configured weights, booking-source and day-of-week skew, and cancellation breakdown.
Analyzes Chili Piper meeting no-show patterns by trigger type, routing path, rep, or workspace to surface actionable optimization opportunities.
Audit all Chili Piper concierge routers for coverage gaps, stale rules, empty distributions, and catch-all overflow.
Apply the same change to many Linear issues at once. Dry-run by default.
Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes
Run the curator — collect signals from configured signal sources and report
Run a compliance gap-assessment for a framework, tie gaps to risk, and produce findings + remediation.
Build a board/executive security brief — strategy, quantified risk, and a board-ready deck.
Run a threat-informed defense cycle for a technique or threat — coverage check, hunt, detection, and purple-team validation.
Deliver a large or multi-stage effort through Hydraia Agile Mode — decompose into an epic, user stories, tasks, subtasks + QA, optionally sync to Jira, then…
Design a new app or service from scratch — guided elicitation, architecture proposals, stack choice, API contract, ADRs — then build it through the full…
Launch the local Hydraia dashboard (status, usage telemetry, editable config) in the browser
Create basic admin dashboard with protected routes. Implement admin route protection with role-based access control. Create dashboard layout with sidebar…
Integrate Google Analytics 4 for comprehensive tracking. Install gtag.js script in application layout. Create analytics wrapper hooks for type-safe event…
Integrate privacy-friendly Plausible Analytics for cookieless tracking. Add Plausible script to application layout with custom domain if configured. Implement…
Start a professional AI/ML research-engineer workflow for a task (any domain - CV, medical imaging, NLP/LLM, tabular, time-series). Researches papers first,…
Extract rules from CLAUDE.md and its referenced documents and compile them into trigger-bound rule files
Aggregate nunchi delivery logs to show per-rule delivery counts and dead rules
Compress this workspace's CLAUDE.md by moving mechanically-triggered rules into just-in-time rule packs. Operator-triggered, never automatic.
Flow registry: extract inventories flows, list shows status, file queues validation tickets.
Push direction: ports local mechanism-script fixes back to the hub as a reviewed PR. Opposite of /update.
Manually delegate a boring, low-risk task to the Antigravity CLI (agy), always reviewing the result.
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project…
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project…
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project…
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit)
Clone a website — a working behavior ARCHIVE (real code + data replayed offline; tabs, filters, transitions work), a pixel-identical editable RESTORE (real…
Judge the current UI blind (render + screenshot if possible), grep the anti-slop patterns, and run the mandatory forced-subtraction pass.
Run the full UIForge pipeline on a brief — thesis, one direction, tokens first, sourced components, budgeted composition, blind critique, forced subtraction.
Keep working toward one durable, verifiable objective with status, pause, resume, complete, clear, diagnostics, soft token budget, deadline, and Stop-hook…
You are helping the user export their journal for backup or sharing.
Is the context layer still true? 0-token staleness + broken-citation audit (no LLM, CI-friendly). Add --status for the fast hash-only subset.
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic