In short:
ak-review-prreviews one or more GitHub pull requests: it reads the description, diff and CI, rates findings on 3 levels, then gives one verdict per PR. When you turn on a flag, it hands fixing toak-fixand pushing and merging toak-git. Without flags it does not fix anything, post anything to GitHub, or merge.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you have the number or link of one or more PRs and want to know what is worth worrying about, or want to go all the way: fix, post the review, merge, green CI. If you only need an opinion on the PR, run it without flags and skip --fix.
flowchart LR
A["Open PR"] --> B["ak-review-pr"]
B --> C["Findings and verdict in chat"]
B -->|"--fix"| D["ak-fix fixes, ak-git cp pushes"]
B -->|"--reply"| E["Formal review on GitHub"]
B -->|"--merge"| F["ak-git merge-pr, watches CI"]Four ideas to hold on to:
| Idea | Question | Example |
|---|---|---|
| Severity | Does this finding block the merge? | Critical: bug, vulnerability, data loss. Important: logic error, missing input check. Suggestion: redundant comment |
| Verdict | Can this PR move on? | Approve with no Critical or Important, Request changes while any remain, Comment when only Suggestions are left |
| Each flag unlocks one step | What is the skill allowed to touch? | No flag: read only. --fix fixes and pushes, --reply posts the review, --merge merges a ready PR |
| Several PRs, one at a time | What happens with 3 PRs at once? | 481 482 490 finishes 481 fully before 482, a failing PR is only recorded |
The fix loop stops when the re-review is clean, when ak-fix needs your decision, when the same finding survives 3 fixes, or when CI breaks and cannot be repaired automatically. If it stops blocked, the PR is not merged, and --merge is permission to merge a ready PR, not an order to force one.
Sample prompt for checking a PR before you approve it:
/ak-review-pr <PR number>| Flag | What it is for | Since ak |
|---|---|---|
--fix | Fixes findings, pushes to the PR branch, then reviews again | 1.0.0 |
--reply | Posts a formal review on the PR | 1.0.0 |
--merge | Merges a ready PR and waits for green CI | 2.4.0 |
--advice | kongming weighs in at key checkpoints | 2.10.0 |
--ultra | 5 independent reviews, merging evidence-backed findings | 2.13.0 |
Below is the detailed version: the run flow, 6 situations with prompts, each flag explained (when to use it, when you do not need it, what you get, which flags it combines with), the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-review-pr: review, fix, post and merge GitHub PRs" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-review-pr". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-review-pr
