agentleFS
Sign inStart free
imrangadzhievimrangadzhiev/anti-slop/skills/pr-hygiene/SKILL.md

pr-hygiene

Skill27 starsChanged 4 months agoMITView on GitHub

Make PRs merge-ready — tight scope, clear description, no leftover debug, honest test notes. Use when opening a PR, writing a PR description, cleaning a branch before review, or when the user mentions pull request, merge-ready, or PR hygiene.

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. a2ui-project/a2ui★ 17ksame name
    2. google/A2UI★ 17ksame name
    3. MaggieAppleton/maggieappleton.com-V3★ 226same 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use this structure (adapt section names to the host: GitHub/GitLab):

    line 20
  2. Distinctive:

    NEVER mix refactor + feature + dependency bump in one PR unless required

    line 49
  3. Distinctive:

    NEVER force-push shared branches without warning

    line 50
  4. Distinctive:

    NEVER open a PR with "tests TBD" and no plan

    line 51
  5. Distinctive:

    NEVER bury breaking changes in the middle of the description

    line 52

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

PR Hygiene

Turn the current work into a PR a human can review in one pass.

Before opening

  • Branch contains one logical change (or clearly labeled stacked commits)
  • No leftover console.log, debugger, TODO: temp, commented-out blocks you added
  • No unrelated formatting-only churn
  • Secrets, .env, and local-only files are not staged
  • Diff matches the stated goal — nothing "extra helpful"

Description template

Use this structure (adapt section names to the host: GitHub/GitLab):

## Summary
<1–3 bullets: what and why>

## Test plan
- [ ] <how you verified>
- [ ] <edge case worth checking>

## Notes
<risks, follow-ups, screenshots if UI>

Commit / PR title

  • Imperative, specific: fix checkout: reject expired discount codes
  • Not: update stuff, fix, WIP, address comments

Reviewer empathy

Call out:

  • Files that look scary but are mechanical (renames, generated)
  • Behavior that changed for callers/API consumers
  • Anything you are unsure about

Anti-patterns

  • NEVER mix refactor + feature + dependency bump in one PR unless required
  • NEVER force-push shared branches without warning
  • NEVER open a PR with "tests TBD" and no plan
  • NEVER bury breaking changes in the middle of the description

If asked to open the PR

  1. Summarize the diff in your own words first
  2. Draft title + body with the template
  3. List residual risks in one short section

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