agentleFS
Sign inStart free
ccoalmccoalm/ccl-skills/skills/worktree-isolation/scripts/AGENTS.md

ccl-skills / scripts

AGENTS.md6 starsChanged 3 months agoApache-2.0View on GitHub

Scripts here inspect or clean git worktrees and branches under the worktree isolation policy. - Destructive cleanup must be conservative: dry-run by default where possible, no force deletion, and never delete dirty, detached, default-branch, or unmerged worktrees. - Default-branch/MR branch cleanup requires platform merge evidence, not only local ancestry. - Path handling must be canonical and must not follow unsafe aliases. - Negative tests are required for protected cases, and they must be sensitive: a negative probe that would still…

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Default-branch/MR branch cleanup requires platform merge evidence, not only local ancestry.

    line 11
  2. Distinctive:

    Run the touched script's tests or a synthetic throwaway-repo matrix.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

skills/worktree-isolation/scripts Agent Contract

Scripts here inspect or clean git worktrees and branches under the worktree isolation policy.

Rules:

  • Destructive cleanup must be conservative: dry-run by default where possible, no force deletion, and never delete dirty, detached, default-branch, or unmerged worktrees.
  • Default-branch/MR branch cleanup requires platform merge evidence, not only local ancestry.
  • Path handling must be canonical and must not follow unsafe aliases.
  • Negative tests are required for protected cases, and they must be sensitive: a negative probe that would still pass with the protecting predicate removed proves nothing. Encode the mutation walk in the suite (see the killing-mutation rule in testing-strategy); test_worktree_sweep.sh probe P7 is the worked instance for this directory.

Validation:

  • Run the touched script's tests or a synthetic throwaway-repo matrix.
  • bash skills/skill-extraction-workflow/scripts/check-ccl-skills.sh .

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