agentleFS
Sign inStart free
eeshsaxenaeeshsaxena/agent-skills/skills/pr-describer/SKILL.md

pr-describer

Skill2 starsChanged 3 months agoMITView on GitHub

Write pull request descriptions a reviewer can approve fast. Use when opening a PR or summarizing a branch of changes.

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. nanoodlecom/noodle-skills★ 2same name
    2. DigitalVanguardSolutions/Skills★ 1same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 these and read the output before writing a word:

    line 14
  2. Distinctive:

    Lead with impact,: not implementation. The reviewer wants to know what changes for users or the system first.

    line 48
  3. Distinctive:

    Keep it honest: If test coverage is thin or a corner is unhandled, say so.

    line 52

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

PR Describer

A good PR description gets reviewed faster and merged sooner because it answers the reviewer's questions before they ask. Build it from the actual diff, never from imagination.

Gather first

Run these and read the output before writing a word:

git log main..HEAD --oneline
git diff main...HEAD --stat

Understand what actually changed. If the diff and your summary disagree, the diff wins.

Structure

## What
One or two sentences. What does this PR do, in plain language.

## Why
The problem or motivation. Link the issue if one exists.

## How
The approach and any notable decisions. Call out trade-offs and things you
considered but rejected.

## Testing
How you verified it works. Commands run, cases covered, screenshots for UI.

## Risk / rollout
Anything that could break, migrations, feature flags, or "safe, fully covered".

Rules

  1. Title is a conventional-commit-style summary of the whole PR, imperative and under ~70 characters.
  2. Lead with impact, not implementation. The reviewer wants to know what changes for users or the system first.
  3. Flag the risky files. Point reviewers at the two or three files that deserve the most attention, so review effort lands where it matters.
  4. Keep it honest. If test coverage is thin or a corner is unhandled, say so. Hidden gaps cost more trust than admitted ones.
  5. Cut boilerplate. Skip sections that do not apply rather than filling them with "N/A" noise.

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