Reset an epic's test data — close PRs, delete branches, reopen issues, revert code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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 operations아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Alias for /flo-simplify — see that skill's 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run /fl on a ticket with moflo's three standing considerations loaded first — cross-platform (Rule
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.