submit-a-pull-request
Skill3 starsChanged 54 days agoMITView on GitHub
Use this skill when the user wants to submit the current local branch as a pull request to a GitHub repository.
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commit-changes-to-gitSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
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 11
Use repository's actual default branch as base.
- Very specific: line 32
Use imperative-mood title, not Fixes or Update.
- Distinctive: line 37
Write body as few short paragraphs.
- Distinctive: line 57
Use closing keyword only when user or commit already cites issue.
- Distinctive: line 61
Read owner from repository slug.
- Distinctive: line 63
Stop when owner stays unknown.
- Distinctive: line 64
Ask user to resolve it.
- Distinctive: line 71
Write few short paragraphs covering change and motivation.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Target
Target GitHub repository user named, or origin otherwise.
Use repository's actual default branch as base.
Resolve base branch at runtime, never hard-coding main.
Preconditions
Refuse on default branch or with dirty working tree. Refuse when no commits sit ahead of default branch. Refuse when open pull request already targets same branch. Confirm branch is up to date with remote default.
Boundaries
Submit commits untouched. Skip editing, amending, rebasing, squashing, building, testing, and linting.
Branch
Push branch before opening pull request.
Title
Use imperative-mood title, not Fixes or Update.
Derive title and body, never from branch name.
Body
Write body as few short paragraphs. Cover what changes, why, and any follow-up. Quote snippet of most important change, no longer than ten lines. Trust code to convey change better than prose.
Format
Shape pull request as imperative title plus short prose body. Shape comment as one or two sentences.
Voice
Write like human.
Vary rhythm, never sliding into AI cadence.
Open with substance, never with boilerplate or buzzword strings.
End body on last sentence.
Skip Generated with footers, Co-Authored-By trailers, and robot emoji.
Closing
Use closing keyword only when user or commit already cites issue.
Owner
Read owner from repository slug. For organization, use top recent committer as owner. Stop when owner stays unknown. Ask user to resolve it.
Example
Branch 42-retry adds retry logic and user says "open PR".
Push branch to origin.
Title pull request Add retry to courier client.
Write few short paragraphs covering change and motivation.
Quote most important change, under ten lines.
Ping owner once in follow-up comment.
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.

