Make Pr
Finish a Remotion-style monorepo feature by formatting affected packages, committing on a non-main branch, and opening a GitHub PR with a title that matches your pr-name skill.
Overview
make-pr is an agent skill for the Ship phase that formats affected packages with Oxfmt, commits on a feature branch, and opens a GitHub pull request titled via the pr-name skill.
Install
npx skills add https://github.com/remotion-dev/remotion --skill make-prWhat is this skill?
- Blocks or fixes work on main by branching when needed
- Runs `bunx oxfmt src --write` on every affected package before commit
- Commits locally then pushes to the remote feature branch
- Creates the PR with `gh` CLI using the same title rules as the pr-name skill
- Pairs with the repo’s pr-name skill for consistent PR titles
Adoption & trust: 1k installs on skills.sh; 49.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have finished feature changes but still need branch checks, package formatting, a clean commit, push, and a correctly titled GitHub PR.
Who is it for?
Solo builders or tiny teams on a Bun monorepo using gh who want a repeatable PR-opening ritual tied to a pr-name convention.
Skip if: Repos without GitHub/gh, projects that do not use Oxfmt or Bun, or workflows where PRs are opened manually with unrelated title schemes.
When should I use this skill?
Open a pull request for the current feature after implementation is complete.
What do I get? / Deliverables
A pushed feature branch with Oxfmt-applied changes and an open gh pull request whose title follows your pr-name skill rules.
- Committed changes on a non-main branch
- Open GitHub pull request via gh
Recommended Skills
Journey fit
Opening and titling a pull request is the handoff from local work into team review—canonical Ship shelf before merge and release. Review subphase covers PR creation, branch hygiene, and pre-merge formatting—exactly what this workflow automates.
How it compares
Use instead of asking the agent to improvise git push and gh pr create steps without your repo’s formatting and pr-name rules.
Common Questions / FAQ
Who is make-pr for?
Developers shipping features from agent-assisted coding sessions who already use GitHub CLI and want branch, format, commit, and PR steps bundled into one skill.
When should I use make-pr?
Use it in the Ship phase when implementation is done and you need a review-ready PR—after local edits on a feature branch (or when the skill must create one because you are on main).
Is make-pr safe to install?
It instructs git commit, push, and gh pr create on your machine; review the Security Audits panel on this page and confirm branch and remote targets before running.
Workflow Chain
Requires first: pr name
SKILL.md
READMESKILL.md - Make Pr
Ensure we are not on the main branch, make a branch if necessary. For all packages affected, run Oxfmt to format the code: ``` bunx oxfmt src --write ``` Commit the changes. The title of the PR must be according to the [`pr-name`](../pr-name/SKILL.md) skill. Push the changes to the remote branch. Use the `gh` CLI to create a pull request and use the same format as above for the title.