agentleFS
Sign inStart free
mournermourner/claudefiles/skills/pr-summary/SKILL.md

pr-summary

Skill15 starsChanged 5 months agoMITView on GitHub

Draft a concise pull-request summary or release note for a branch or diff. Focuses on the crux of the change, verifies claims against the diff, and outputs a draft for review (never posts).

  • Commits and pushes

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use benchmark, explain and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dragonflydbSkill

    benchmark

    Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".

    Also in 3 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • VercelSkill

    investigate

    Investigate an issue report, or analyze the constraints of a proposed change, with strict, evidence-driven diagnosis.

    Also in 3 projects that use this

  • SentrySkill

    onboard

    Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.

    Also in 3 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Default to the current branch against its merge base (usually main).

    line 11
  2. Distinctive:

    Don't assert what you haven't checked: Every claim should trace to a real change in the diff.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 16 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 summary

Produce a draft for the user to review — never post it. No gh pr create/edit or issue/PR comments unless asked after seeing the draft.

Default to the current branch against its merge base (usually main); ask only if that's ambiguous.

  • Read the diff first (git diff <base>...HEAD) — write from what actually changed, not from memory or the branch name.
  • Describe the net change vs base, not the journey. Summarize the final diff, not the steps taken to get there — skip intermediary fixes that only make sense relative to an earlier work-in-progress state, not vs main.
  • Lead with the crux: the why and the impact. Group changes at a high level; don't enumerate every minor edit (renames, moved lines, incidental cleanup). A reviewer should get the point from the first line or two.
  • Compact and plain. Short declarative sentences, no marketing language, no emoji, no filler sections. Match the repo's existing PR/changelog style.
  • Don't assert what you haven't checked. Every claim should trace to a real change in the diff. Numbers you already measured this session are fine to reuse as long as no later change invalidated them — only re-measure when something affecting them changed. Sizes in decimal KB (1000-based).

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