- Home
- Skills
- Code Quality & Review
- Adversarial PR Review
More screenshots
Works with the AI Agents you already use
Adversarial PR Review
Adversarial pull request review: riskiest files first, tries to break the change, and returns a few paste-ready, line-anchored PR comments. Works for teammates' PRs and self-review.
$5
Adversarial PR Review
Example session with this skill installed
Review https://github.com/rikuws/mood./pull/8 — it's a teammate's PR I've been asked to review. Read-only: don't post anything to GitHub.
- Read your context and instructions
- Compiled the adversarial pr review
Mode: Teammate's PR (full pass). Reviewed at head f5817f3, base main @ 91674ea. 12 files, +228 / −9.
The key question - Does the new note/verdict data survive every path that rewrites an item: sync dedupe, older app builds, and the capture flows that still write the user's words into text?
Documentation/AGENT_API.md:104 - should-fix
The new contract says text is captured source material … But every capture path still puts what the user typed into text: CaptureSheet on Mac (CaptureSheet.swift:60/142), ManualCaptureView on iOS (ManualCaptureView.swift:54/112) and the Share extension (ShareComposerModel.swift:118). … Say in both AGENT_API.md and skills/mood-distill/references/agent-api.md:62 that text can still hold the user's capture-time note until the capture sheets write to note.
Shared/Models/Inspiration.swift:23 - question
The PR body says "An older app build that edits an item will drop note/verdict on save". It's wider than edits. … An iPhone that hasn't updated and re-shares a saved post is enough to wipe a note written on the Mac. …
Sync/Sources/SyncMerger.swift:254 - question
nil now means both "never judged" and "the user picked Undecided" … the merge copies the other copy's reject back → the reset is undone without any sign. …
Review summary - A small, well-scoped schema addition … The real risk is outside the diff. … Fix the agent-doc caveat before merge. The two questions need the author's call.
Already raised: Integration with #9 (citableText(.note, of:) returning nil) - rikuws …
Not reviewed: I didn't build or run the tests (no macOS/Xcode in this environment). …
Connects securely to your tools. The creator never sees your data.
About this skill
Built by a dev who reviews PRs daily. Reviewing a teammate's pull request is a chore you can't skip, and skimming it gets you ten naming nits and misses the bug. This skill does the part that takes the time: it works out what the change is for and where the risk is, then tries to break it.
What you get
- A short orientation: the PR's intent, what really changed, the one key question, and where to start reading.
- The riskiest files read first. Big PRs are split into 3-6 layers, and refactors are kept apart from behaviour changes.
- An adversarial pass: hidden assumptions, hostile inputs, retries and races, old data, rollbacks, and callers that weren't updated.
- At most 5 findings, each anchored to
file:lineand ready to paste as a PR comment, with asuggestionblock for small, certain fixes.
Modes
- Teammate's PR is the default.
- Your own PR adds author checks (leftover debug code, scope creep, missed callers, missing tests) and ends with a "fix before requesting review" list.
- Quick pass covers only the riskiest files, with at most 3 findings and no nits.
- Harsh / red-team also questions the design.
Safe by default. It's read-only. It posts a review only when you ask and say yes, and it never approves or requests changes for you.
Works with GitHub PRs through gh, or with any local branch or diff through git.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.
Reports at most 5 findings in a normal pass and 3 in a quick pass unless you ask for more. Doesn't edit or fix code: patches are only offered, never applied without your yes. Never approves or requests changes on GitHub; posting is opt-in and uses COMMENT only. GitHub inline comments only work on lines inside the diff, so other findings go in the review body. Lockfiles, generated code, snapshots and vendored files are skimmed by name only. The PR description writer it mentions is a separate skill; without it, it drafts a short description itself.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 22 days ago
- Accounts
GitHub
- Software
Git
- Optional
GitHub CLIripgrep
GitHub CLI, signed in, is only for GitHub pull requests; local branches and diffs need only Git.
Permissions
Allowed Hosts
File Scopes
Read-only by default: never edits, commits, pushes or posts unless you explicitly say yes. Posting is one GitHub review with event COMMENT; it never approves or requests changes on your behalf. gh pr checkout is used only if a local copy helps, and it asks first if the working tree has changes.