agentleFS
MithunWijayasiriMithunWijayasiri/dotclaude/skills/orchestrate/SKILL.md

orchestrate

Skill4 starsChanged 21 days agoMITView on GitHub

Use when a large mechanical multi-file change — sweep, rename, translation, build/fix loop — should run in stages. Handles survey, per-stage briefs, diff review, and a commit per stage.

170 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use define-requirements, orchestrate-plan 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.
  • sson0-erSkill

    define-requirements

    Work with the user, one question at a time, to complete the requirements document (docs/claudex/<slug>/01-requirements.md). Run by the orchestrator (parent). Stays out of design and implementation.

    Also in 3 projects that use this

  • EternallLightSkill

    orchestrate-plan

    Use when executing a locked, reviewed PLAN.md by delegating the implementation to visible worker agents in Orca, herdr, or cmux ONE PHASE at a time — splitting the plan into context-window-sized phases, giving every phase a pristine worker context, and (when the plan touches INDEPENDENT repos) running one worker per repo IN PARALLEL. Triggers on "run the plan with a worker", "execute the plan in the other pane", "split the plan into phases and build it with workers", "build the backend and frontend in parallel panes". Not for edits you can finish inline; outside Orca, herdr, or cmux use tgc-skills:orchestrate.

    Also in 3 projects that use this

  • sson0-erSkill

    record-evidence

    How to record external facts (docs, command output, codebase findings) as evidence and design choices as decisions. Used by the researcher, designer and reviewer agents.

    Also in 3 projects that use this

  • PinkneyJiangSkill

    improve-architecture

    扫描代码库中的架构摩擦点,识别浅模块并挖掘深模块演进机会。生成可视化交互式 HTML 诊断报告,并在用户确认后闭环实施深度重构。

    Also in 4 projects that use this

  • kjnezSkill

    ticket

    Work on a JIRA/Linear ticket end-to-end: read ticket details, explore codebase, create a branch, implement with TDD, run quality checks, update ticket status, and create a PR. Use when the user provides a ticket ID to implement. Triggers on requests like "/ticket PROJ-123", "work on this ticket", "implement PROJ-123".

    Also in 4 projects that use this

  • xfstudioSkill

    reverse-engineer

    Expert reverse engineer specializing in binary analysis,

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 152 edited versions we read keep these.

  • 6

    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:

    Read the plan/task, repo rules (CLAUDE.md), and grep the scope: hit counts per pattern, files per area, exact line numbers of …

    line 17
  2. Distinctive:

    Create branch (repo convention) before any agent runs.

    line 20
  3. Distinctive:

    Verify commands to run and fix until green (build, test, format check), with expected warning/test counts.

    line 36
  4. Distinctive:

    Never commit, push, or branch.

    line 38
  5. Distinctive:

    Check the worker's Uncertain list item by item.

    line 57
  6. Distinctive:

    Run build + test + format yourself, quiet output (grep summary lines).

    line 59

“Common” is measured: kept by at least 6 in 10 of the 152 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

Main session = planner + reviewer. Sonnet subagents = workers. Goal: token-heavy edits (file sweeps, renames, translations, build/test loops) run on the cheaper model and stay out of main context; main spends tokens only on survey, briefs, and review.

Pays off vs. not

  • Pays: mechanical or repetitive edits across many files, long build/fix loops, work whose raw output (diffs, logs) main never needs to read.
  • Doesn't: a handful of tool calls (round-trip + brief cost more than doing it), work needing many judgment calls the user must make, stages that can't be specified precisely. Say so and do it inline instead.

1. Survey + align (main)

  • Read the plan/task, repo rules (CLAUDE.md), and grep the scope: hit counts per pattern, files per area, exact line numbers of non-mechanical spots. Precise briefs depend on this; vague briefs → wrong work.
  • Working tree or index not clean (git status --short non-empty) → stop until the user commits or stashes; review needs a diff that holds only the stage.
  • Collect open decisions → ask user (recommended option first). Ask once, upfront: "commit each stage after review + green build?" Declined → pause after each green stage until the user commits. Push/PR = separate ask, always.
  • Create branch (repo convention) before any agent runs.

2. Split into stages

  • One stage = one reviewable commit, at most one rename pair (e.g. rename structure → content/strings → second rename).
  • Stages touching the same files → sequential. Disjoint files within one stage → parallel agents in one message; still one review, one commit.
  • Each stage leaves the build green.

3. Brief (one Agent call per stage)

Agent(model: "sonnet", subagent_type: "general-purpose"). Brief is the worker's only context:

  • Repo path, branch, what earlier stages already did, "read CLAUDE.md first" + its hard rules (warnings-as-errors, encoding/BOM/line endings, style).
  • Goal in one line + "Do" list: exact paths, line numbers, literal before → after strings.
  • "Do NOT touch" list: files/names reserved for later stages or out of scope.
  • File moves via git mv; delete nothing except build outputs.
  • Verify commands to run and fix until green (build, test, format check), with expected warning/test counts.
  • Final grep for old names; list every remaining hit with a one-word reason.
  • Never commit, push, or branch. Ambiguity → minimal option + list under "Uncertain".
  • Report: short, no raw diffs. Grouped changes, counts, verify results, remaining-grep list, Uncertain.

4. Review (main) — never trust the report

Worker's own grep only checks old names → misses mangled new names (e.g. every fetchUser became fetchUserUser, worker reported clean).

  • Worker not green or no report → don't review; send it back once, then stop and tell the user.
  • Stage the stage's paths only (git status --short lists them; never git add -A — it sweeps in unrelated files), then git diff --cached -M --stat | tail -1. Read git diff --cached -M --summary — renames, mode changes, creates/deletes don't show in the line filter.
  • Residual filter — print only lines a plain rename doesn't explain. OLD/NEW = the stage's rename pair; renames removed lines only, so mangled and reversed names still show. OLD is a sed regex → escape ., [, * (a\.b):
    git diff --cached -M -U0 | sed '/^-/s/OLD/NEW/g' \
      | awk 'function flush(  i, n) { n = nr > na ? nr : na; for (i = 1; i <= n; i++) if (r[i] != a[i]) print h "\t-" r[i] "\t+" a[i]; nr = na = 0; split("", r); split("", a) }
          /^diff /{flush(); h=""; next} /^\+\+\+ /&&h==""{f=substr($0,5); next} /^@@/{flush(); h=f" "$2; next}
          h!=""&&/^-/{r[++nr]=substr($0,2)} h!=""&&/^\+/{a[++na]=substr($0,2)} END{flush()}'
    Pairs each hunk's removed and added lines in order → cross-file swaps and reordered lines show. Read every residual line.
  • Stages with no rename pair (strings, translations, build/fix loops) → read the whole staged diff (git diff --cached -U0).
  • Mangle check: grep new name glued to extra letters, e.g. grep -rnE "[A-Za-z]NEW|NEW[A-Za-z]", and odd variants (doubled prefix, wrong case).
  • Check the worker's Uncertain list item by item.
  • Small fix → edit inline, re-stage, re-run the filter. Larger → SendMessage to same agent with the exact problem (keeps its context).
  • Run build + test + format yourself, quiet output (grep summary lines). Checks rewrote tracked files → re-stage the stage's paths and re-run the filter. Green → commit (if approved) with Conventional Commit subject → next stage. Red → no commit, no next stage; fix or send back.

5. Report

  • Table: commit SHA + one-line what.
  • Subagent tokens per stage (from task notifications) + bugs caught in review.
  • Manual test list (UI, external integrations) the agents couldn't run.

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.