agentleFS
Sign inStart free
Obedience-CorpObedience-Corp/fresh/skills/fresh/SKILL.md

fresh

Skill4 starsChanged 32 days agoApache-2.0View on GitHub

Start clean after a merged PR. Puts the repo on its default branch, level with the remote, and removes branches and worktrees that already landed (squash merges included). Use when someone says "/fresh", "my PR merged", "clean up my branches", or "start fresh".

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. rayketcham-lab/qn-claude-web★ 2same name
    2. lucasyhzhu-debug/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Get camp: Run bash "<skill-dir>/scripts/ensure-festival.sh".

    line 25
  2. Very specific:

    Preview: Follow output.md to capture camp fresh --dry-run.

    line 28
  3. Very specific:

    Run: Use the capture command for camp fresh, with the same requested flags.

    line 29
  4. Very specific:

    Use -b <branch> in both commands if the user named what is next.

    line 30
  5. Very specific:

    When camp says it linked the repository or created the festival camp, repeat that line to the user, including camp project unlink.

    line 48
  6. Very specific:

    Never force-delete a branch that camp kept.

    line 56

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

/fresh

Your PR merged. Start clean.

<skill-dir> is the directory containing this SKILL.md (Claude Code prints it as "Base directory for this skill"). Never guess it. Run camp from the user's project repo.

  1. Get camp. Run bash "<skill-dir>/scripts/ensure-festival.sh". It prints the path to camp on stdout; use that path below. It installs or updates Festival only if needed and says so on stderr. Tell the user what it said.
  2. Preview. Follow output.md to capture camp fresh --dry-run. Show the plan unedited; stop if it fails.
  3. Run. Use the capture command for camp fresh, with the same requested flags. Use -b <branch> in both commands if the user named what is next.
  4. Report. Display the captured visual, kept work, warnings, and any undo line.

Done means: default branch synced with origin, merged work cleaned up, and on the requested next branch if one was given. Report anything camp kept.

When it stops

  • Step 1 exits 3. Festival could not be installed or updated. Say what the script said and stop.
  • Step 1 exits 4 or 5. This camp cannot yet freshen a repository that is not in a camp. Run the preview anyway; it works if the repository is already linked. If it says "not in a camp", say so in one or two plain sentences, give any update command the script printed, and stop. Do not do the git work by hand.
  • camp asks for --campaign. Show the camps it listed, ask which one, then rerun steps 2 and 3 with --campaign <name>. Do not pick.

When camp says it linked the repository or created the festival camp, repeat that line to the user, including camp project unlink. Never let it be silent.

Laws

  • One repository, one outcome.
  • Preview first. Every time.
  • Uncommitted changes stop the run. Ask; never stash or commit for the user.
  • Never force-delete a branch that camp kept.

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