commit-pr
Skill1 starsChanged 4 days agoMITView on GitHub
Propose a short git commit subject and a copy-pasteable markdown PR description for the current changes. Use when asked for a commit message, commit subject, or PR description.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- ZaxbyHub/opencode-swarmtheir own version, first seen Oct 30, 2026
- zaxbysauce/opencode-swarmtheir own version, first seen Oct 8, 2026
- videojs/video.jstheir own version, first seen Oct 8, 2026
- samuelclay/NewsBlurtheir own version, first seen Oct 8, 2026
- tiantaiyang/claude-skillstheir own version, first seen Aug 27, 2026
- parthsidpara/lazyskillstheir own version, first seen Aug 3, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- videojs/video.js★ 40ksame name
- samuelclay/NewsBlur★ 7.7ksame name
- zaxbysauce/opencode-swarm★ 519same name
- ZaxbyHub/opencode-swarm★ 518same name
- parthsidpara/lazyskills★ 1same name
- pujakesuma/my-claude-skills★ 1same name
- tiantaiyang/claude-skills★ 0same 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 repository4 other files it gives its agents.
- implement-ticketSkill
- improve-codebaseSkill
- jira-ticketSkill
- review-branchSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
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 17
Read git status --short, git diff, and git diff --staged.
- Distinctive: line 18
Read git log --oneline -10 to match commit conventions.
- Distinctive: line 20
If staged and unstaged changes differ, briefly state that the output covers staged changes.
- Distinctive: line 25
Use imperative mood, match the repository's prefix convention, and omit a trailing period.
- Distinctive: line 28
Start with one summary line explaining the purpose, then a blank line and short bullet points covering relevant behavior changes or …
- Very specific: line 35
Put each output in a separate fenced code block, using a markdown fence for the PR description.
- Distinctive: line 36
Follow each block with its character count.
- Distinctive: line 37
Add at most one line of commentary.
“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
Commit and PR description
Provide the following for the current changes:
- A git commit description 50 characters or fewer.
- A copy-pasteable markdown PR description 400 characters or fewer.
Propose only; do not commit, push, or create a PR.
Inspect
- Read
git status --short,git diff, andgit diff --staged. - Read
git log --oneline -10to match commit conventions. - Describe staged changes when present; otherwise use the full working diff, inspecting relevant untracked files.
- If staged and unstaged changes differ, briefly state that the output covers staged changes.
Write
- Commit description: 50 characters or fewer. Use imperative mood, match the repository's prefix convention, and omit a trailing period. Describe the change, not a file list.
- PR description: 400 characters or fewer. Start with one summary line explaining the purpose, then a blank line and short bullet points covering relevant behavior changes or reviewer context. Omit headings, badges, footers, and boilerplate.
Verify and present
- Measure both strings with a command, counting all characters, including spaces, newlines, and markdown.
- Shorten and remeasure until both limits pass; report only measured counts.
- Put each output in a separate fenced code block, using a
markdownfence for the PR description. - Follow each block with its character count; exclude fences and count labels from the limits.
- Add at most one line of commentary.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.