make-pr
Skill316 starsChanged 5 months agoMITView on GitHub
Use when the user is ready to submit work for review and wants a GitHub pull request opened — e.g. "open PR", "create pull request", "prepare PR", "make PR", "submit for review".
- Reads credentials
- Commits and pushes
10 other projects use a version of this.
Adopted by
Most recently taken up by
- hamlim/skillstheir own version, first seen Nov 1, 2026
- foldkit/foldkittheir own version, first seen Oct 8, 2026
- TracecatHQ/tracecattheir own version, first seen Oct 8, 2026
- remix-run/remixtheir own version, first seen Oct 8, 2026
- linhvu0711/skillstheir own version, first seen Sep 24, 2026
- dnywh/skillstheir own version, first seen Sep 16, 2026
Used with
Projects with it also use commit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- remix-run/remix★ 33ksame name
- TracecatHQ/tracecat★ 3.9ksame name
- foldkit/foldkit★ 1.1ksame name
- Neko-Catpital-Labs/Invoker★ 21same name
- linhvu0711/skills★ 2same name
- tf63/vetol★ 2same name
- zahardev/aicontext★ 2same name
- davidemastricci/skills★ 1same name
- dnywh/skills★ 1same name
- hamlim/skills★ 1same 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-content-typeSkill
- add-localeSkill
- add-ui-componentSkill
- consolidate-patternsSkill
- copy-componentSkill
- create-content-componentSkill
- find-componentSkill
- find-skillsSkill
- frontend-designSkill
- next-best-practicesSkill
- remove-azure-monitorSkill
- remove-cache-revalidationSkill
- remove-cdn-purgeSkill
- remove-sentrySkill
- resolve-review-suggestionsSkill
- review-prSkill
- seed-contentSkill
- start-workSkill
- strapi-schema-checkSkill
- validate-branch-refsSkill
- vercel-react-best-practicesSkill
- write-testsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 8 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Commit / branch conventions: apps/docs/docs/reference/workflow.md.
- Distinctive: line 17
Be automated: Do not ask for confirmations unless something is genuinely ambiguous.
- Distinctive: line 27
If multiple, separate with spaces.
- Very specific: line 37
If on dev or main, abort: "You're on a base branch.
- Very specific: line 41
Default dev. Override via $ARGUMENTS.
- Distinctive: line 81
Commit. If the pre-commit hook (Lefthook + commitlint) fails:
- Distinctive: line 94
If rejected for remote-ahead, abort: tell the user to pull/rebase first.
- Very specific: line 102
Check for a PR template at .github/pull_request_template.md (also .github/PULL_REQUEST_TEMPLATE.md or .github/PULL_REQUEST_TEMPLATE/).
- Distinctive: line 106
When a template is present, apply these mapping rules:
- Distinctive: line 117
Leave human-only items unchecked (Assignee, Reviewers, Labels, screenshots, etc.)
- Very specific: line 121
If the template has no Task Link section but an issue was resolved, prepend Closes #<num> above the body.
- Very specific: line 133
Use a tempfile via mktemp to avoid shell-escaping the multi-line body.
- Very specific: line 155
Never push with --force or --force-with-lease unless the user explicitly asks.
- Very specific: line 156
Never --amend after a hook failure.
- Distinctive: line 157
Don't reference Asana, Linear, or Jira — they're out of scope for v1.
- Distinctive: line 158
If multiple issues plausibly match the branch number, ask the user.
“Common” is measured: kept by at least 6 in 10 of the 9 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
Create Pull Request
Commit any uncommitted work in logical groups, push, then open a pull request (a merge request on GitLab) filled against the project PR template. GitHub is automated end-to-end via gh; on other hosts the work is still committed and pushed, and you hand the user a ready-to-open PR/MR link.
Commit / branch conventions: apps/docs/docs/reference/workflow.md.
Be automated. Do not ask for confirmations unless something is genuinely ambiguous. Only stop to ask the user if you cannot resolve the issue link or the diff is too large to summarize confidently.
Arguments
Optional $ARGUMENTS:
- A base branch name → use as merge target (default:
dev) - A GitHub issue URL or
#<number>→ fetch viagh issue viewand link in PR body - Free-text → treat as additional context for the description
If multiple, separate with spaces. Auto-detect each arg by shape.
Phase 1 — Gather context
1.1 Determine current branch
git branch --show-currentIf on dev or main, abort: "You're on a base branch. Switch to a feature branch first."
1.2 Determine base branch
Default dev. Override via $ARGUMENTS. Verify it exists with git rev-parse --verify <base>. Fall back to main if dev missing.
1.3 Analyze all changes since branching
Run in parallel:
git diff <base>...HEAD --statgit diff --statgit diff --cached --statgit status --shortgit log <base>..HEAD --oneline
Read actual diffs:
git diff <base>...HEADgit diff
1.4 Resolve issue link (optional)
Resolution order — stop at first match:
$ARGUMENTScontains a GitHub issue URL or#<number>→ fetch withgh issue view <num> --json title,body,url.- Branch name contains
<digits>at the end (e.g.feat/foo-284) → trygh issue view <num>and verify the title looks related. - Skip — leave issue link out of the PR body.
Auto-fetch uses gh, so it resolves GitHub issues only. On other hosts (or if gh is missing/unauthenticated), skip the fetch and continue — the branch's ticket id still lands in the title/body.
Phase 2 — Smart commits
Skip if working tree is clean.
Grouping rules
- Dependency changes (
package.json,pnpm-lock.yaml) → separate commit:chore(deps): update dependencies. - Remaining changes → group by logical context. One context = one commit. Don't split fix + its test into two.
For each group
- Stage explicit files:
git add <file...>(never-Aor.). - Generate a conventional commit subject (
type(scope): subject, under 50 chars). Type from branch prefix (feat/→feat, etc.) or change context. - Commit. If the pre-commit hook (Lefthook + commitlint) fails:
- Read the error.
- Fix lint/format/commitlint complaint.
- Re-stage and create a new commit (do NOT
--amend).
Phase 3 — Push & open PR
3.1 Push
git push -u origin HEADIf rejected for remote-ahead, abort: tell the user to pull/rebase first.
3.2 Title
Concise conventional-commit-style subject. Under 70 chars. Example: fix(ui): footer renders wrong colour on dark mode.
3.3 Body — fill the PR template
Check for a PR template at .github/pull_request_template.md (also .github/PULL_REQUEST_TEMPLATE.md or .github/PULL_REQUEST_TEMPLATE/). If present, fill it in and preserve its structure exactly.
If no template file exists (current state of this starter), build the body from these sections: a 2–4 sentence Description (WHY before WHAT), a one-line TL;DR, New environmental variables (or None), and a short Test plan. Then skip to "Create PR".
When a template is present, apply these mapping rules:
- Task Link → if an issue was resolved in Phase 1, replace placeholder URL with the real one. Otherwise leave the placeholder.
- Description → 2–4 sentences. WHY before WHAT. Reference root cause if it's a fix.
- TL;DR → one sentence.
- Screenshots/Videos →
N/Aif no UI change, otherwise leave the prompt for the author to fill. - New environmental variables → list any new env vars touched in the diff (grep diff for
process.env.adds,.env*edits). If none, writeNone. - Checklist – author → tick only what the diff clearly satisfies:
Descriptiononce writtenEnvironmental variablesif you listed them or wroteNoneUnit/Integration testsif test files were added- Leave human-only items unchecked (Assignee, Reviewers, Labels, screenshots, etc.)
- Before merging → leave all unchecked.
- Checklist – reviewer → leave all unchecked.
If the template has no Task Link section but an issue was resolved, prepend Closes #<num> above the body.
3.4 Open the PR
Detect the remote host from git remote get-url origin:
GitHub, with
ghavailable:gh pr create --base "<base>" --title "<title>" --body-file <tmpfile>Use a tempfile via
mktempto avoid shell-escaping the multi-line body. Parse the output for the PR URL.Any other host, or
ghmissing/unauthenticated — the branch is already pushed, so don't fail. Print the title and body and hand the user a ready-to-open link for the detected host:- GitLab →
<repo-web-url>/-/merge_requests/new?merge_request%5Bsource_branch%5D=<branch> - Bitbucket →
<repo-web-url>/pull-requests/new?source=<branch> - Azure Repos / unknown host → confirm the push and tell the user to open the PR in their host's UI against
<base>.
Derive
<repo-web-url>from the origin remote (strip a trailing.git, convertgit@host:org/repotohttps://host/org/repo).- GitLab →
Report
Print:
PR/MR: <url> (or "open manually — link printed above")
Branch: <branch> -> <base>
Commits on branch: <n>
Issue: <#num title> (or "no issue linked")Notes
- Never push with
--forceor--force-with-leaseunless the user explicitly asks. - Never
--amendafter a hook failure. - Don't reference Asana, Linear, or Jira — they're out of scope for v1.
- If multiple issues plausibly match the branch number, ask the user.
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.

