agentleFS
Sign inStart free
OutThisLifeOutThisLife/brooklyn-skills/skills/cpr/SKILL.md

cpr

Skill207 starsChanged 4 months agoMITView on GitHub

Clean the diff, then open or refresh the PR/MR — one pass, ending in the linked URL. Use for /cpr, "clean and PR", "tidy it up and push the PR", or any handoff where polish and the PR should happen together.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill 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:

    Run the two skills for real — this file is the sequence, not a replacement for their contents.

    line 14
  2. Distinctive:

    Don't stall on a clean pass.

    line 37

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

CPR (clean → PR)

clean then pr-update, in that order, without asking between them. Use it when the work is done and the branch should end up as a PR someone can read.

Run the two skills for real — this file is the sequence, not a replacement for their contents.

Steps

  1. Clean (clean). Re-read the diff, cut dead code and debug logging, extend existing helpers instead of paralleling them, match neighboring style. Polish only — this is not a test/tsc/lint run.
  2. Shape + publish (pr-update). Topical commits, title and body that describe the change as a whole, media in an existing body preserved verbatim, prose through no-tropes.
  3. End with the PR/MR as a markdown link — number and full forge URL.

Order matters

Clean first, always. Committing then cleaning means the commit split describes code you already threw away, and the PR body describes a diff that no longer exists.

Stop conditions

  • UI work: don't start until the user likes the UI (ui-only).
  • Nothing to clean is a valid outcome — say so in one line and go to step 2.
  • Don't stall on a clean pass. If polish keeps expanding, that's scope creep; ship the narrow version.

Scope

  • In: polish the diff, shape commits, create or update the PR/MR, print the link.
  • Out: CI and review threads (pr-ready), triage/salvage (pr-triage), stacked bases (stacked-pr), merging.

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