agentleFS
hranesshraness/personal-monorepo-template/.agents/skills/pr-cleanup/AGENTS.md

personal-monorepo-template / pr-cleanup

AGENTS.md4 starsChanged 48 days agoMITView on GitHub

The file

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

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Keep this copy synchronized with the pr-cleanup skill in Jungle and the personal monorepo template.

    line 8
  2. Distinctive:

    Keep repository and organization scope dynamic.

    line 9
  3. Distinctive:

    Do not add automatic branch deletion, force pushes, workflow cancellation, releases, deployments, or provider mutations.

    line 11

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

Contents

  • SKILL.md – live-census, recovery, readiness, merge, supersession, retention, and post-merge workflow.
  • agents/openai.yaml – skill-list metadata and default $pr-cleanup invocation.

Guidelines

  • Keep this copy synchronized with the pr-cleanup skill in Jungle and the personal monorepo template.
  • Keep repository and organization scope dynamic; never hardcode an owner's repository list.
  • Preserve mutation authority boundaries, exact-head readiness, non-force branch retention, post-merge verification, and the final live census.
  • Do not add automatic branch deletion, force pushes, workflow cancellation, releases, deployments, or provider mutations.
  • Pair any future deterministic mutation helper with focused tests and an audit-only default.

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.