English | 日本語
PR templates, chosen for you.
GitHub lets you keep several pull request templates, but gives you no way to pick one when you open a PR. So most teams end up with one template that fits nothing well.
omakase-pr is a skill for Claude Code and Codex. Leave it to the chef: it reads your branch, commits, and diff, picks the right template for the kind of change, fills it in, and opens the PR with gh pr create.
> omakase
Opened https://github.com/acme/shop/pull/412
Kind: fix, from the branch name fix/login-timeout.
The body follows .github/PULL_REQUEST_TEMPLATE/fix.md: the bug, the root cause, the fix, and how it was tested. Checkboxes are ticked only when there is evidence, like tests in the diff. It never claims testing that did not happen.
The title says what changed in under 60 characters, not which files you touched. The body takes under a minute to read: the point and where to look, not a retelling of the diff. If nothing says why the change was made, it asks you instead of making up a reason.
The first time you run it, omakase-pr looks at your recent branch names and commit messages and proposes a prefix config:
# .github/omakase-pr.yml
kinds:
feature: [feat, feature]
fix: [fix, bugfix, hotfix]
refactor: [refactor]
docs: [docs]
chore: [chore, ci, build, deps]
# Optional. Uncomment to set these on every PR.
# assignees: ["@me"]
# labels:
# feature: [enhancement]
# fix: [bug]
# projects: [Roadmap]
# milestone: v1.2Assignees, labels (per kind), projects, and a milestone are left empty. Uncomment the ones you want, and every PR gets them.
Then it generates one template per kind in .github/PULL_REQUEST_TEMPLATE/. If you already have a template, its sections are kept as your house style in every kind. Templates come in English and Japanese, matched to the language of your recent PRs and commits. You review both before anything is committed.
- The kind you name:
omakase fix - Your branch name:
fix/login-timeout - Your commit messages:
fix: handle expired session - The diff itself: only docs touched means docs
If it still cannot tell, it asks you once.
/plugin marketplace add 6igtree/omakase-pr
/plugin install omakase-pr@omakase-pr
git clone https://github.com/6igtree/omakase-pr.git /tmp/omakase-pr
mkdir -p ~/.agents/skills && cp -r /tmp/omakase-pr/skills/omakase-pr ~/.agents/skills/Requires the GitHub CLI (gh), logged in.
Try it without creating anything first:
omakase preview
It shows the kind, the title, and the body. Nothing is pushed. When it looks right, open the PR:
omakase
Add whatever you need in plain words, in any combination:
omakase fix, as a draft
omakase with reviewer @alice and label urgent
What you say for one PR wins over the config.
omakase init runs the setup again. In Claude Code, /omakase-pr works too.
MIT