When a PR lands, the first question in your head usually isn't "is this code correct", it's "did
the
dev read it back even once before sending it".
open-pr exists for exactly that: a Claude Code plugin that reviews PRs against the conventions
your
repo already has, remembers what you tell it, and goes through the same procedure every run — same
tone, same severity scale, same trail left on the PR.
Works with GitHub (.../pull/<n>) and GitLab (.../-/merge_requests/<n>, self-hosted
included).
Why not just a generic review skill?
| What usually happens | open-pr |
|---|
| No way to tell whether the dev reviewed their own PR | The dev runs /open-pr:review on their own PR; a reviewer sees it right in the conversation |
| Advice at the level of generic rules, off the project's conventions | Reads the repo's README/CLAUDE.md/AGENTS.md/docs/wiki, and team rules beat every generic one |
| You say it once, next time it's the same again | You mention it in chat → it asks to write it into that repo's memory → next run applies it |
| Fixes arrive as commit spam, amends, force-pushes, no replies | Exactly 1 commit per run, no history rewriting, and a reply on every comment once pushed |
How it runs
flowchart LR
A[New PR] --> B["/open-pr:review URL"]
B --> C{Repo set up?}
C -- not yet --> D["One short round of questions<br/>+ read the repo's conventions"]
D --> E[Review inside its own worktree]
C -- yes --> E
E --> F["Post 1 review<br/>🔴 🟠 🔵 📝 · clean → LGTM 🌟"]
F --> G["/open-pr:fix URL"] --> H["1 commit + a reply per finding"]
F --> I["You mention it in chat"] --> J["Written into the repo's memory"]
J -. next run .-> B
Full flow, re-review, and the check fix makes before it touches a file:
How it works.
What comes out
One review, three parts that belong together: the overview, a comment on the exact line with the
corrected code, and the reply fix leaves on that same thread once the change is pushed.
Full size, and the same review in the language each repo picks:
What a review looks like.
Install
/plugin marketplace add TOMOSIA-VIETNAM/open-pr
/plugin install open-pr@open-pr
Update:
/plugin marketplace update open-pr
/plugin update open-pr@open-pr
/reload-plugins
/open-pr:upgrade
You also need Claude Code, plus gh for GitHub
PRs or glab for GitLab MRs, logged in — the review is posted
through that account.
Usage
| Command | What it does |
|---|
/open-pr:review <URL> | Reviews the PR and posts exactly 1 review: overview + line-by-line comments. Never edits code, never closes, never merges. The first run in a repo also sets it up |
/open-pr:fix <URL> | Reads the findings that review left, fixes the code, wraps it in 1 commit, then replies per comment. 🔵/📝 always ask you first |
/open-pr:upgrade | Brings a repo's local config up to the current schema. Summarises what changes and asks; nothing is written until you agree |
/open-pr:clean | Removes the worktrees review checked PR code out into — each is a full checkout on disk. Lists them with their size and asks first; memory and settings are never touched |
Where to stand, what each command writes, every setting: Configuration.
What it reviews
- Bugs & logic
- Security
- Performance
- Code quality
- Maintainability & readability
- Framework/language-specific — from that stack's own template
Your team's rules outrank all six.
Every criterion in detail, and the priority order when they conflict:
What it reviews.
Contributing? See CONTRIBUTING.md.
Context cost per release
Enjoy reviewing 🥰
