mcpField
P
pr-hygiene

pr-hygiene

github.com/imrangadzhievDevelopment2751 installsUpdated 14w ago
Repository

About pr-hygiene

pr-hygiene is a checklist and drafting skill for preparing a focused, reviewable pull request. It helps developers check branch scope and staged files, then write a structured description and specific title.

Key features

  1. 01Check branch scope and logical changes
  2. 02Look for debug leftovers and unrelated edits
  3. 03Check staged files for secrets and local files
  4. 04Draft a structured PR description
  5. 05Write specific imperative PR titles
  6. 06Summarize reviewer concerns and residual risks

Use cases

  1. 01Prepare a focused change for review
  2. 02Check a diff before opening a PR
  3. 03Draft a GitHub or GitLab PR description
  4. 04Document behavior changes and remaining risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/imrangadzhiev/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