agentleFS
Sign inStart free
eric-cieloeric-cielo/moflo/.claude/skills/reset-epic/SKILL.md

reset-epic

Skill19 starsChanged 3 months agoMITView on GitHub

Reset an epic's test data — close PRs, delete branches, reopen issues, revert code

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Delete local branches: Delete any local branches matching the same patterns (skip the current branch)

    line 26
  2. Very specific:

    Clear epic-state memory: Delete all entries in the epic-state memory namespace for this epic and its stories (keys: epic-<N>, story-<N> for …

    line 29
  3. Distinctive:

    Never delete main or the current branch

    line 47
  4. Very specific:

    Use gh CLI for all GitHub operations

    line 48
  5. Distinctive:

    If a revert of merged code is needed, note it but DO NOT auto-revert (ask the user first)

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/reset-epic - Reset Epic Test Data

Fully resets an epic so it can be re-tested from scratch.

Arguments: $ARGUMENTS

Usage

/reset-epic <epic-number>     # e.g. /reset-epic 287, to reset that epic for retesting

What It Does

Given an epic issue number, perform ALL of the following:

  1. Identify stories: Parse the epic body for linked issue numbers
  2. Close open PRs: Find all open PRs referencing any story number or the epic number. Close them.
  3. Delete remote branches: Find and delete any remote branches related to the epic (e.g., epic/<number>-*, feat/<story>-*, revert/epic-<number>-*)
  4. Delete local branches: Delete any local branches matching the same patterns (skip the current branch)
  5. Reopen issues: Reopen all story issues and the epic itself if any were closed
  6. Uncheck task lists: Edit the epic body to uncheck all - [x] checkboxes back to - [ ]
  7. Clear epic-state memory: Delete all entries in the 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.
  8. Verify clean state: Confirm all stories are OPEN, no related PRs are open, no related branches exist, and epic-state memory is empty

Output

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

Important

  • Never delete main or the current branch
  • Use gh CLI for all GitHub operations
  • If a revert of merged code is needed, note it but DO NOT auto-revert (ask the user first)
  • This is a destructive operation — confirm with the user before executing if there are merged PRs that might need code reverts

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free