agentleFS
Sign inStart free
ek33450505ek33450505/claude-agent-team/skills/wizard/SKILL.md

wizard

Skill8 starsChanged 32 days agoMITView on GitHub

Multi-step workflow with human-approval gates before destructive operations. Use when a task involves irreversible actions like mass file writes, database migrations, git force-push, dependency removal, or infrastructure changes.

  • Deletes or force-pushes
  • Commits and pushes

170 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, writing-beats and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 56 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 49 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 41 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 54 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 47 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a step fails after approval, do NOT retry automatically — report and wait for instructions

    line 38
  2. Distinctive:

    Never batch unrelated destructive operations into a single approval

    line 40

“Common” is measured: kept by at least 6 in 10 of the 154 edited versions of this file we could read. “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

Wizard Mode Activated

For the remainder of this task, enforce a step-by-step approval gate before every destructive or irreversible operation.

What Counts as Destructive

  • File operations: Deleting files, overwriting >3 files at once, rm -rf, mv of directories
  • Git operations: git push --force, git reset --hard, git branch -D, amending published commits
  • Database operations: DROP, TRUNCATE, DELETE without WHERE, schema migrations
  • Dependency changes: Removing packages, major version upgrades, changing build tooling
  • Infrastructure: Modifying CI/CD, changing environment variables, altering deploy configs
  • External systems: Sending emails, posting to APIs, creating/closing PRs or issues

Workflow

For each destructive step:

  1. Announce — State what you're about to do and why
  2. Show impact — List exactly what will be affected (files, rows, branches, etc.)
  3. Show rollback — Explain how to undo if something goes wrong
  4. Wait — Ask for explicit "yes" / "go" / "approved" before proceeding
  5. Execute — Perform the action only after approval
  6. Confirm — Report the result immediately after execution

Rules

  • Non-destructive operations (Read, Glob, Grep, git log, git diff) proceed without gates
  • If a step fails after approval, do NOT retry automatically — report and wait for instructions
  • Group related small changes (e.g., 3 import edits in one file) into a single gate
  • Never batch unrelated destructive operations into a single approval

Deactivation

Wizard mode ends when the current task is complete, or say "deactivate wizard mode".

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