Reset an epic's test data — close PRs, delete branches, reopen issues, revert code
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Fully resets an epic so it can be re-tested from scratch.
Arguments: $ARGUMENTS
/reset-epic <epic-number> # e.g. /reset-epic 287, to reset that epic for retesting
Given an epic issue number, perform ALL of the following:
epic/<number>-*, feat/<story>-*, revert/epic-<number>-*)- [x] checkboxes back to - [ ]epic-state memory namespace for this epic and its stories (keys: epic-<N>, story-<N> for each story). Use mcp__moflo__memory_list with namespace epic-state to find entries, then mcp__moflo__memory_delete for each.Print a summary table:
Epic #<N> Reset Summary
─────────────────────────
Issues reopened: X
PRs closed: X
Branches deleted: X (remote) / X (local)
Status: CLEAN — ready for retesting
main or the current branchgh CLI for all GitHub operationsNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Turn a vague idea into a concrete, actionable spec through a short Socratic dialogue, then hand the result off to an existing moflo surface — a /flo ticket, a spell, or memory. Use BEFORE you have a defined unit of work, when the goal is still fuzzy.
The English summary is being prepared. Showing the original description.
Scaffold new spell step commands and connectors. Use when building new step commands for spells or extending the spell engine with new capabilities. Connectors are for new I/O transport types OR platforms requiring complex multi-step interaction (e.g., browser-based automation).
The English summary is being prepared. Showing the original description.
Alias for /flo-simplify — see that skill's description.
The English summary is being prepared. Showing the original description.
Structured multi-hop web research with explicit confidence gating — plan the inquiry, search (WebSearch/WebFetch), score your own confidence, and keep digging until the answer is well-supported or a hop cap is hit, then emit a cited synthesis. Learns across sessions by storing each research case to memory and reusing prior strategies. Use when a question needs more than one search — comparisons, current-best-practice questions, anything where a single lookup leaves you unsure.
The English summary is being prepared. Showing the original description.
Consult the Eldar — audit a project's moflo + Claude Code setup for portable, high-leverage gaps and guide remediation. Default mode is read-only audit with severity-ranked findings; --fix presents an interactive triage menu and walks the user through each chosen fix (healer, missing CLAUDE.md, sparse guidance, hook/MCP wiring, empty memory namespaces, stack→guidance gaps). Use when starting in a new project, when Claude feels lost or inefficient, when guidance/CLAUDE.md is sparse, or as a periodic health check.
The English summary is being prepared. Showing the original description.
Run /fl on a ticket with moflo's three standing considerations loaded first — cross-platform (Rule
The English summary is being prepared. Showing the original description.