create-pull-request
Skill30 starsChanged 16 days agoApache-2.0View on GitHub
Create or update GitHub pull requests for this repository with Conventional Commit titles aligned to their changeset summaries. Use whenever asked to open, create, draft, or retitle a pull request.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- ErikaAX08/erikas-skillstheir own version, first seen Nov 8, 2026
- marcellocurto/skillstheir own version, first seen Nov 8, 2026
- openflocon/Flocontheir own version, first seen Nov 1, 2026
- StephanMeijer/skillstheir own version, first seen Nov 1, 2026
- tada5hi/skillstheir own version, first seen Nov 1, 2026
- vrodokanakis/claude-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use grilling and frontend-design.
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.
GoogleSkillgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- cline/cline★ 71ksame name
- makeplane/plane★ 62ksame name
- bitwarden/clients★ 14ksame name
- microsoft/vscode-pull-request-github★ 2.6ksame name
- Mapsui/Mapsui★ 1.6ksame name
- warpdotdev/oz-skills★ 825same name
- platformplatform/PlatformPlatform★ 439same name
- openflocon/Flocon★ 379same name
- haru/redmine_ai_helper★ 107same name
- kimrgrey/claudini★ 9same name
17 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-changesetSkill
- e2e-testsSkill
- instrumentationSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use the GitHub CLI for GitHub operations.
- Very specific: line 19
Use feat for a feature and fix for a bug fix.
- Very specific: line 21
Use ! immediately before the colon for a breaking change.
- Distinctive: line 22
Keep the description concise and representative of the entire pull request.
- Distinctive: line 24
If the branch contains a changeset whose first summary line accurately describes the pull request, reuse that line verbatim as the pull …
- Distinctive: line 25
When the branch contains multiple changesets, prefer one shared Conventional Commit summary for all of them and the pull request title.
- Distinctive: line 26
If intentionally distinct changeset summaries cannot share an accurate title, preserve their meaning and call out the mismatch rather than …
- Distinctive: line 28
If no changeset exists, derive a Conventional Commit title from the complete branch diff.
- Distinctive: line 31
Before creating or updating the pull request, run:
- Distinctive: line 37
Do not create the pull request with a non-conforming title.
- Distinctive: line 38
If the user supplied a non-conforming title, preserve its meaning while converting it to the required format and state the resulting title.
“Common” is measured: kept by at least 6 in 10 of the 27 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
Create a Pull Request
Inspect the branch diff and any changeset files added or modified by the branch before choosing the pull request title. Use the GitHub CLI for GitHub operations.
Title
The pull request title must follow Conventional Commits 1.0.0:
<type>[optional scope][optional !]: <description>Use feat for a feature and fix for a bug fix.
Other meaningful types such as docs, test, refactor, build, ci, and chore are allowed.
Use ! immediately before the colon for a breaking change.
Keep the description concise and representative of the entire pull request.
If the branch contains a changeset whose first summary line accurately describes the pull request, reuse that line verbatim as the pull request title. When the branch contains multiple changesets, prefer one shared Conventional Commit summary for all of them and the pull request title. If intentionally distinct changeset summaries cannot share an accurate title, preserve their meaning and call out the mismatch rather than silently rewriting release notes.
If no changeset exists, derive a Conventional Commit title from the complete branch diff. Reuse that exact title if a changeset is subsequently created for the same pull request.
Before creating or updating the pull request, run:
node scripts/release/validate-changesets.mjsDo not create the pull request with a non-conforming title. If the user supplied a non-conforming title, preserve its meaning while converting it to the required format and state the resulting title.
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.