agentleFS
Sign inStart free
omdenkar2-uiomdenkar2-ui/all-in-one/skills/aio-worktree/SKILL.md

aio-worktree

Skill0 starsChanged 31 days agoMITView on GitHub

Set up isolated backend work ownership without discarding or silently copying unrelated changes.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Use the host managed-worktree capability when suitable, verify the returned path/attachment and run required setup/checks.

    line 14

≈ “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

AIO Worktree

Set up isolated backend work ownership without discarding or silently copying unrelated changes.

Protocol

  1. Inspect repository/status and available attached worktrees; prefer a suitable existing isolated checkout. Distinguish the actual repo from an ancestor directory containing unrelated user files.
  2. Choose the user-specified ref or appropriate current task base, name owned paths/interfaces and preserve the original checkout. Never invent a starting branch that changes the accepted source.
  3. Use the host managed-worktree capability when suitable, verify the returned path/attachment and run required setup/checks. Uncommitted work is not implicitly copied; handle needed changes explicitly.
  4. Assign disjoint unit ownership and one canonical integrator. Archive/delete only task-owned disposable work after preserving needed artifacts and observed delivery; never blanket-reset a shared checkout.

Return and handoff

A verified isolated checkout/ownership packet and setup evidence, with preserved user state.

In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.

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