pr-description
Skill1 starsChanged 2 months agoMITView on GitHub
Generate PR description from commits and diff. Args: [<base-branch>]
94 other projects use a version of this.
Adopted by
Most recently taken up by
- TangleML/tangle-uitheir own version, first seen Nov 9, 2026
- taecontrol/skillstheir own version, first seen Nov 8, 2026
- sankalpaacharya/skillstheir own version, first seen Nov 8, 2026
- joel611/skillstheir own version, first seen Nov 8, 2026
- Wade-DevCode/awesome-coding-skills-cntheir own version, first seen Nov 8, 2026
- AlessioScarfone/skillstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use ao-desktop-dev, bug-triage and 10 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.
agentlab-inSkillao-desktop-dev
Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually verify AO frontend changes in the actual desktop app rather than ao preview, dev:web, or mock data.
Also in 4 projects that use this
jMertaSkillbug-triage
Use when the user reports a bug, regression, runtime error, failing build, or broken test and wants reproduction, diagnosis, root-cause analysis, or an authorized fix. Isolates the shared cause and verifies the smallest relevant change.
Also in 4 projects that use this
GitHubSkillcommit-message
Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help
Also in 9 projects that use this
saffron-healthSkilladdress-review
Address PR review comments systematically. Use when responding to code review feedback on a pull request.
Also in 3 projects that use this
NVIDIASkillwriting-docs
Use when adding or changing user-facing behavior or documentation in Megatron-Energon, or when creating new .py, .sh or .md files that need license headers.
Also in 3 projects that use this
Sagargupta16Skilldependency-audit
Audit project dependencies for security vulnerabilities, licensing issues, maintenance health, and optimization opportunities. Use it during regular security audits (monthly or quarterly); before a major release when you want to ensure the dependency tree is clean; when evaluating whether to adopt or replace a dependency; after a security advisory affects one of your dependencies; when your install times or bundle sizes have grown noticeably.
Also in 3 projects that use this
Other versions94 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 94
- jdx/mise★ 36ksame name
- zulip/zulip★ 26ksame name
- Nagi-ovo/gemini-voyager★ 21ksame name
- pipecat-ai/pipecat★ 17ksame name
- AgentWrapper/agent-orchestrator★ 14ksame name
- ComposioHQ/agent-orchestrator★ 14ksame name
- OrchestratorInc/agent-orchestrator★ 14ksame name
- Untrivial-ai/agent-orchestrator★ 14ksame name
- sanity-io/sanity★ 6.4ksame name
- vimeo/psalm★ 5.9ksame name
84 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 repository17 other files it gives its agents.
- check-drySkill
- check-testsSkill
- create-commit-messageSkill
- create-unit-testsSkill
- deslop-proseSkill
- deslopSkill
- fanout-reviewSkill
- fix-security-auditSkill
- framework-upgrade-guideSkill
- generate-adrSkill
- learnSkill
- optimizeSkill
- resolve-merge-conflictsSkill
- security-checkSkill
- ship-itSkill
- takeawaysSkill
- update-claude-mdSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 89 edited versions we read keep these.
2
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
- Distinctive: line 62
If no step applies, write "Manual smoke-test recommended: exercise the changed area in the running app." rather than fabricating a …
- Very specific: line 69
If excluded files are >5% of the diff line count, note in ## Notes: "Lockfile/generated delta: N files, ~M lines: excluded from review …
- Distinctive: line 71
Do not narrate steps. Output only the formatted PR description.
“Common” is measured: kept by at least 6 in 10 of the 89 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
<!-- Note: $ARGUMENTS is substituted by Claude commands only. In Copilot,
the user must include their argument inline in the prompt; the skill
body sees the literal text "$ARGUMENTS" unsubstituted. -->Arguments
[<base-branch>]
- Optional. The branch to diff against; defaults to
main. - Examples:
/pr-description,/pr-description develop
Copilot CLI note:
$ARGUMENTSdoes not substitute in skills; include the argument inline in your prompt.
Generate a pull request description for the current branch.
Base branch from $ARGUMENTS (default: "main").
Steps:
- Get branch name:
git branch --show-current - Get commit list:
git log <base-branch>..HEAD --pretty=format:"- %s" --no-merges - Get changed files:
git diff <base-branch>..HEAD --name-status - Get diff summary:
git diff <base-branch>..HEAD --stat
Format output as:
Summary
<1-2 sentence description of what this PR does and why>
Changes
<bullet list from commits, grouped by area if possible>
Files Changed
<list from diff --name-status, grouped by type: Added / Modified / Deleted>
How to test
- <step 1>
- <step 2>
Notes
<any breaking changes, dependencies, or deploy considerations>
Infer testing steps using this routing table: first match wins, list the matching steps in ## How to test:
| Changed file shape | Test step to include |
*.test.* / *.spec.* / tests/** only | "Run <project test command>: added/updated tests cover the change." |
API route file (e.g., routes/, controllers/, *Controller.*, app.py Flask routes) | "Hit the endpoint with curl/Postman: curl <method> <url>: expect <status> and <body shape>." |
| Database migration | "Run the migration on a dev DB, then run the reverse, then re-run forward. Confirm schema matches <file>." |
UI component (.vue, .tsx, .jsx) | "Open the affected view in the running app (<dev command>), exercise the changed interaction, confirm <expected visible result>." |
| Config / build / CI file | "Re-run the affected pipeline locally (e.g., npm run build, ./scripts/check.sh): confirm no new warnings or failures." |
Docs-only (.md, .rst, docs/**) | "Read for clarity; no functional test needed." |
| Mix of the above | List one step per category, in the order above. |
If no step applies, write "Manual smoke-test recommended: exercise the changed area in the running app." rather than fabricating a procedure.
Exclude from ## Files Changed:
- Lockfiles (
package-lock.json,yarn.lock,pnpm-lock.yaml,Cargo.lock,poetry.lock,Gemfile.lock,go.sum), unless the PR stated purpose is a dependency upgrade. - Generated files matching
dist/,build/,*.min.*,coverage/. - The auto-generated
CHANGELOG.mdif the PR uses semantic-release or similar.
If excluded files are >5% of the diff line count, note in ## Notes: "Lockfile/generated delta: N files, ~M lines: excluded from review surface."
Do not narrate steps. Output only the formatted PR description.
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.