agentleFS
hranesshraness/personal-monorepo-template/.agents/skills/reclaim-disk-space/AGENTS.md

personal-monorepo-template / reclaim-disk-space

AGENTS.md4 starsChanged 49 days agoMITView on GitHub

The file

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

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default to read-only auditing and require exact paths for deletion.

    line 10
  2. Distinctive:

    Never add force deletion, recursive directory sweeps, branch deletion, or dirty-state overrides.

    line 11
  3. Distinctive:

    Keep worktree eligibility dependent on a fresh remote-target fetch, an empty porcelain status, and an ancestor check.

    line 12
  4. Very specific:

    Default to the remote's symbolic HEAD and require --target <remote>/<branch> when that target is unavailable or intentionally different.

    line 14
  5. Distinctive:

    Treat user state and application databases as non-cache data unless the user explicitly accepts their loss.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

Contents

  • SKILL.md – cautious disk-audit, classification, deletion, and verification workflow.
  • scripts/worktree-cleanup.ts – audit-first removal of exact registered, clean, merged Git worktrees.
  • scripts/worktree-cleanup.test.ts – parser, safety-classification, and argument coverage.
  • agents/openai.yaml – skill-list metadata and default invocation prompt.

Guidelines

  • Default to read-only auditing and require exact paths for deletion.
  • Never add force deletion, recursive directory sweeps, branch deletion, or dirty-state overrides.
  • Keep worktree eligibility dependent on a fresh remote-target fetch, an empty porcelain status, and an ancestor check.
  • Protect both the actual primary worktree and the worktree from which the script is invoked.
  • Default to the remote's symbolic HEAD and require --target <remote>/<branch> when that target is unavailable or intentionally different.
  • Treat user state and application databases as non-cache data unless the user explicitly accepts their loss.

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.