pr
Skill293 starsChanged 10 days agoMITView on GitHub
Use for /pr, or 'create a PR' / 'open a pull request' — creates a pull request for the current branch against the repo's base branch with a formatted title and body. Not for reviewing an existing PR (review-pr).
- Commits and pushes
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 6
Create a pull request for current branch targeting the repo's base branch.
- Very specific: line 11
Not this: reviewing an existing PR → /review-pr.
- Very specific: line 41
Create PR via GitHub CLI: gh pr create --base "{base}" --title "$TITLE" --body "$BODY" — never --fill, never an empty body (the pr-format …
- Very specific: line 49
Do NOT auto-merge — explicit /pr means "please review this"
≈ “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
Create a pull request for current branch targeting the repo's base branch.
When to invoke
User says: "/pr", "create a PR", "open a pull request", "push this up for review", or the current branch is ready to be reviewed against the base branch.
Not this: reviewing an existing PR → /review-pr.
Execution boundary
The Git and GitHub mechanics are deterministic and run inline. The main loop keeps only the judgment work: summarize the diff, draft the review text, and show the exact title/body before the external PR creation.
What to do
- Determine which repo — if the user mentions a managed repo (listed in
egregore.json→repos[]), create the PR there. Otherwise use the hub. - Resolve the configured integration branch first:
It prints the branch name; for a managed repo runbash bin/base-branch.shbash bin/base-branch.sh <repo-name>. A non-zero exit means the configuration could not be resolved: stop before any Git change. Use the printed name wherever{base}appears below. - Summarize branch changes vs base branch
- Draft title and body per
.claude/context/pr-format.md:- Title:
type(scope): imperative summary(≤ 72 chars) — the same grammar as commit subjects (.claude/context/commit-format.md). A single-commit PR reuses its commit subject verbatim when it describes the whole PR. - Body:
## What(1–4 bullets) ·## Why(1–3 sentences) ·## Verification(how it was checked — required when the diff touches non-markdown files; be honest if unverified) ·## Risk/## Linkswhen real · attribution footer of the harness that authored the body (final non-blank line, e.g.🤖 Generated with [Claude Code](https://claude.com/claude-code)) - Show the draft to the user; apply their edits before creating
- Title:
- Create PR via GitHub CLI:
gh pr create --base "{base}" --title "$TITLE" --body "$BODY"— never--fill, never an empty body (thepr-formatCI check fails bare PRs) - Track PR in graph (fire-and-forget):
bash bin/graph-op.sh record-pr <number> "<title>" 2>/dev/null &<number>comes from thegh pr createoutput URL; the command resolves the session, repository, and author itself. - Return PR URL
- Do NOT auto-merge — explicit
/prmeans "please review this"
Example
> /pr
Creating pull request...
Branch: feature/2026-01-20-mcp-authentication
Base: main
Commits: 3 commits ahead of main
Changes: +78 lines, -5 lines, 3 files
Title: feat(mcp): add API key authentication
(from your last commit — edit? y/n)
> n
Description — summarize what this PR does:
> Adds API key validation to MCP server. Keys are checked against env var. Includes tests.
Creating PR via GitHub CLI...
gh pr create --base main --title "..."
✓ PR #42 created: https://github.com/{github_org}/myapp/pull/42
PR targeting main — ready for review.Next
Share the PR link. Run /handoff if ending your session.
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.

