agentleFS
Sign inStart free
ChurchCRMChurchCRM/CRM/.agents/skills/source-command-prune-branches/SKILL.md

source-command-prune-branches

Skill989 starsChanged 6 days agoMITView on GitHub

Delete local and your own merged remote branches

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the user asks to run the migrated source command prune-branches.

    line 8
  2. Distinctive:

    Delete local branches whose work has landed, and optionally your own merged remote branches.

    line 14
  3. Very specific:

    Wait for a yes. Then re-run the same command with --apply <plan id> from the preview.

    line 17

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

source-command-prune-branches

Use this skill when the user asks to run the migrated source command prune-branches.

Command Template

/prune-branches

Delete local branches whose work has landed, and optionally your own merged remote branches.

  1. node scripts/maintainer/prune-branches.js (add --remote to include origin). It is a dry run: show the output to the user.
  2. Wait for a yes. Then re-run the same command with --apply <plan id> from the preview. It deletes nothing if the branches changed since the preview.

The script never touches master, the current branch, a branch checked out in a worktree, a branch with an open PR (any author), or a branch with unmerged work. A branch is deleted only when its tip is merged into origin/master or equals the head of one of your merged PRs. Remote branches are deleted only for your own merged PRs, never security/*.

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