pr-summary
Skill1 starsChanged 12 days agoMITView on GitHub
Draft a pull request title and description for the current branch against its base branch (open PR base, else release/0.2 for 0.2 tasks, else main). Use when the user runs /pr-summary. Does not open or push the pull request.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- acfatah/skillstheir own version, first seen Nov 15, 2026
- spencerldixon/skillstheir own version, first seen Nov 8, 2026
- timurgaleev/vibestacktheir own version, first seen Nov 8, 2026
- snuffish/dotfilestheir own version, first seen Nov 1, 2026
- Esi-Abolfazl/skillstheir own version, first seen Oct 20, 2026
- hmj1026/dhpktheir own version, first seen Oct 13, 2026
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.
dragonflydbSkillbenchmark
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
sunnyclinches44Skillexplain
Explains code using real-world analogies and ASCII diagrams
Also in 3 projects that use this
VercelSkillinvestigate
Investigate an issue report, or analyze the constraints of a proposed change, with strict, evidence-driven diagnosis.
Also in 3 projects that use this
SentrySkillonboard
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
AWSSkillretro
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
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- scenario-labs/skills★ 3.5ksame name
- selfxyz/self★ 1.3ksame name
- scenario-labs/blender-plugin★ 962same name
- gittower/git-flow-next★ 458same name
- divinevideo/divine-mobile★ 265same name
- rabble/nostrvine★ 265same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- kjnez/claude-code-django★ 177same name
- gricha/dangerous-skills★ 38same name
12 more not listed
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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agentinit-vitest.mdcCursor rule
- .cursor/rules/git-commits.mdcCursor rule
- .cursor/rules/io-safety.mdcCursor rule
- .cursor/rules/pure-modules.mdcCursor rule
- .cursor/rules/registry-content.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- commit-changesSkill
- implement-taskSkill
- new-featureSkill
- refactorSkill
- review-archSkill
- review-taskSkill
- write-fragmentSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Follow the workflow in docs/workflows/pr-summary.md exactly.
“Common” is measured: kept by at least 6 in 10 of the 18 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.
Files
Follow the workflow in docs/workflows/pr-summary.md exactly. Draft the title and description only; do not open a pull request.
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
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.