pr
Skill24 starsChanged 32 days agoMITView on GitHub
Open a pull request with conventional title, structured description, and pre-flight checks.
- Commits and pushes
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- commitSkill
- debug-teachSkill
- imprint-example-refresh-releaseSkill
- imprint-google-flights-live-auditSkill
- imprint-reteach-auditSkill
- imprint-teach-deepdiveSkill
- pr-review-convergenceSkill
- releaseSkill
- commitSkill
- debug-teachSkill
- imprint-auth-compile-logSkill
- imprint-reteach-auditSkill
- imprint-teach-deepdiveSkill
- prSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 20
Run these in parallel and report results:
- Distinctive: line 27
If any fail, show the errors and ask the user whether to proceed or fix first.
- Distinctive: line 31
Run these to understand the branch:
- Very specific: line 58
Run git remote -v and git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null to check if the branch is pushed.
- Very specific: line 60
If not pushed, run git push -u origin <branch>.
≈ “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
PR Skill
Open a pull request for the current branch with proper conventions.
Step 1 — Pre-flight checks
Run these in parallel and report results:
bun run lint
bun run typecheck
bun testIf any fail, show the errors and ask the user whether to proceed or fix first.
Step 2 — Gather context
Run these to understand the branch:
git branch --show-current— current branch namegit log main..HEAD --oneline— commits on this branchgit diff main..HEAD --stat— files changed
Step 3 — Determine PR title
The PR title must be a conventional commit format: <type>(<scope>): <description>
Pick type and scope the same way as the /commit skill, but based on the overall branch intent (not individual commits).
Step 4 — Write PR description
Use this structure:
## Summary
- Bullet 1: what changed and why
- Bullet 2: key design decisions
- Bullet 3: anything reviewers should pay attention to
## Test plan
- [ ] Tests pass locally
- [ ] Specific scenario testedStep 5 — Check remote
Run git remote -v and git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null to check if the branch is pushed.
If not pushed, run git push -u origin <branch>.
Step 6 — Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"Show the PR URL to the user when done.
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.

