mcpField

pr-hygiene

github.com/icodecraftTesting & quality2747 installsUpdated 14w ago
Repository

About pr-hygiene

pr-hygiene is a code-review skill for preparing focused, reviewable pull requests. It checks change scope and artifacts, then guides the title, description, and risk notes.

Key features

  1. 01Check scope and staged files
  2. 02Use a PR description template
  3. 03Write specific imperative titles
  4. 04Surface reviewer concerns
  5. 05Avoid risky PR practices

Use cases

  1. 01Check a branch before opening a PR
  2. 02Draft a summary and test plan
  3. 03Explain behavior changes and residual risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/icodecraft/anti-slop --skill pr-hygiene

After installing, type/pr-hygienein Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported