Who it is forA developer who has finished a change locally and wants a review pass before creating the pull request.
The problemProblems found after a PR is open add noise to the forge history and slow down the team.
The outcomeA printed review of the committed, uncommitted and untracked files, with no comment posted anywhere.
What you need first
- Node 18 or newer
- gh (GitHub), glab (GitLab) or az (Azure DevOps) installed and logged in to an account that can comment on the PR
- delegate-skills installed, with two delegate lanes named review-main and review-debate created once with $delegate-setup
- Git 2.31 or newer, only for Azure DevOps
Steps
- Run
npx skills add amElnagdy/review-skillsto install the skills. - Run
Use $delegate-setup to add two lanes: review-main on claude at high effort and review-debate on codex at high effort.if the lanes do not exist yet. - Run
node <skill-dir>/scripts/review-pr.mjs --localfrom inside the repo to review the working tree. (inferred, check the README) - Read the printed findings and fix the blocking ones before you open the PR.
Prompt for your agent
In the amElnagdy/review-skills repo, run the debate-review skill with --local on <repo path> against the base branch. Output the P0 and P1 findings with file and line. Verify that nothing was posted to any forge.
Caveat. Local mode rejects non-UTF-8 Git paths, and --dry-run still needs a live PR, so it cannot replace the local preview.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for amElnagdy/review-skills and "Check uncommitted work with a review before opening a PR"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer