generate-pr-description
Skill9 starsChanged 3 months agoMITView on GitHub
Generate PR title and description from branch diff
7 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Ronnasayd/aipptheir own version, first seen Oct 20, 2026
- jealous-sound/azerothcore-wotlk-coatheir own version, first seen Oct 8, 2026
- mod-playerbots/azerothcore-wotlktheir own version, first seen Oct 8, 2026
- azerothcore/azerothcore-wotlktheir own version, first seen Oct 8, 2026
- carlosedm10/skillstheir own version, first seen Aug 8, 2026
- kimgoetzke/coding-agent-configstheir own version, first seen Apr 30, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- gologo13/agent-skills★ 086% same
Wrote their own version · 6
- azerothcore/azerothcore-wotlk★ 9.2ksame name
- mod-playerbots/azerothcore-wotlk★ 449same name
- jealous-sound/azerothcore-wotlk-coa★ 327same name
- kimgoetzke/coding-agent-configs★ 2same name
- carlosedm10/skills★ 1same name
- Ronnasayd/aipp★ 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 repository43 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- agent-risk-reviewSkill
- agent-work-receiptSkill
- automation-roi-auditSkill
- blind-spot-passSkill
- code-reviewSkill
- commit-changes-mainSkill
- commit-same-branchSkill
- commitSkill
- create-pr-mainSkill
- debug-issueSkill
- decision-auditSkill
- define-agent-goalSkill
- design-agent-loopSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- gauntlet-loopSkill
- generate-api-docsSkill
- git-sync-workspaceSkill
- instruction-ablationSkill
- light-review-existing-diffsSkill
- lint-fixSkill
- lint-suiteSkill
- merge-open-prsSkill
- optimize-performanceSkill
- pathfinderSkill
- prompt-eval-debugSkill
- refactor-codeSkill
- requirement-to-implementationSkill
- run-all-tests-and-fixSkill
- scoped-auditSkill
- security-auditSkill
- seo-auditSkill
- setup-new-featureSkill
- structure-promptSkill
- tddSkill
- thermo-nuclear-code-quality-reviewSkill
- update-memory-bankSkill
- update-readmeSkill
- write-unit-testsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
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
- Distinctive: line 8
Create a comprehensive pull request description based on the changes in this branch and format it as proper markdown for use in a GitHub PR …
- Distinctive: line 24
Use closing keywords if this PR resolves issues
- Distinctive: line 45
Always include a test plan describing how the changes were verified.
- Distinctive: line 46
Use Conventional Commits style for the PR title when appropriate.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Overview
Create a comprehensive pull request description based on the changes in this branch and format it as proper markdown for use in a GitHub PR description.
Steps
- Summary
- Provide a clear, concise summary of what this PR accomplishes
- Changes Made
- List the key changes made in this PR
- Include both code and non-code changes
- Highlight any breaking changes
- Testing
- Describe how the changes were tested
- Include any new test cases added
- Note any manual testing performed
- Related Issues
- Link to any related issues or tickets
- Use closing keywords if this PR resolves issues
- Additional Notes
- Any deployment considerations
- Follow-up work required
- Notes for reviewers
Generate PR Description Checklist
- Provided clear, concise summary of what this PR accomplishes
- Listed all key changes made in this PR
- Highlighted any breaking changes
- Described how the changes were tested
- Included any new test cases added
- Noted any manual testing performed
- Linked to any related issues or tickets
- Included any deployment considerations
- Noted any follow-up work required
- Formatted as proper markdown for GitHub PR
Guardrails
- Always include a test plan describing how the changes were verified.
- Use Conventional Commits style for the PR title when appropriate.
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.