pr
Skill0 starsChanged 5 months agoMITView on GitHub
Create a branch name, short commit message, and pull request title and description. Use when the user asks to open or prepare a PR, write a commit message, or name a branch for the current changes.
In this repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 10
Use only read-only git commands (git status, git diff, git log).
- Very specific: line 26
After the prefix, the branch name is lowercase, hyphen-separated, and short (roughly 2–5 words), e.g.
- Very specific: line 34
type: must match the branch prefix (e.g.
- Distinctive: line 70
Use your judgement — err on the side of brevity unless the changes genuinely need more context.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Inspect the current branch's staged changes, unstaged changes, and untracked files to understand what has changed. Then produce a semantic branch name, a Conventional Commits message, and a pull request title and description.
Also check the recent git log — if the repository's history already follows different conventions (different prefixes, types, or message style), prefer the repository's conventions over the defaults below.
Use only read-only git commands (git status, git diff, git log). Do not create branches, commits, or pull requests — output the suggestions for the user to apply.
Branch prefix conventions
| Prefix | Use for |
feature/ | new features |
fix/ | bug fixes |
hotfix/ | urgent production fixes |
refactor/ | code cleanup with no behaviour change |
perf/ | performance improvements |
docs/ | documentation only |
test/ | tests only |
ci/ | CI/CD pipeline changes |
chore/ | maintenance (deps, tooling, config) |
After the prefix, the branch name is lowercase, hyphen-separated, and short (roughly 2–5 words), e.g. feature/add-checklist-search.
Commit message — Conventional Commits format
<type>(<optional scope>): <short description>- type must match the branch prefix (e.g.
feature/→feat,fix/→fix,docs/→docs,chore/→chore,perf/→perf,test/→test,ci/→ci,hotfix/→fix) - scope is optional; use the affected module, file, or area (e.g.
auth,readme,api) - description is lowercase, imperative mood, no trailing period, ≤ 72 chars total
Pull request description — scale to complexity
Assess the size and impact of the changes, then choose the appropriate level of detail:
Minor (trivial edits, single file, obvious intent — e.g. typo fix, small config tweak):
- One-sentence summary. No sections needed.
Moderate (a few files changed, self-contained feature or fix):
## Summary
- <bullet points describing what changed and why>
## Test plan
- <checklist of what to verify>Complex (many files, architectural change, breaking change, or non-obvious motivation):
## Summary
<short paragraph: what this does and why>
## Changes
- <key change 1>
- <key change 2>
## Breaking changes
<describe any, or remove this section if none>
## Test plan
- <checklist of what to verify>Use your judgement — err on the side of brevity unless the changes genuinely need more context.
Output format
Wrap the PR description body in a fenced markdown code block so the raw markdown is easy to select and copy from the terminal.
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.