# AI use cases for Review Skills (amElnagdy/review-skills) Repo: [amElnagdy/review-skills](https://github.com/amElnagdy/review-skills) | Use cases: 4 | Page: https://dedupedai.com/use-cases/amelnagdy-review-skills/ A GitHub, GitLab, and Azure DevOps review tool where two AI models debate a pull request, one review with inline comments is posted from your own account, and a babysitter works the review rounds. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Get a two-model review on a GitHub pull request: https://dedupedai.com/use-cases/amelnagdy-review-skills/second-opinion-github-pr-review/ - Check uncommitted work with a review before opening a PR: https://dedupedai.com/use-cases/amelnagdy-review-skills/review-local-changes-before-pr/ - Work reviewer threads on a PR until it is merge-ready: https://dedupedai.com/use-cases/amelnagdy-review-skills/babysit-pr-to-merge-ready/ - Run a two-model review on a GitLab merge request: https://dedupedai.com/use-cases/amelnagdy-review-skills/review-gitlab-merge-request/ ## How to get a two-model review on a GitHub pull request with Review Skills Repo: [amElnagdy/review-skills](https://github.com/amElnagdy/review-skills) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Two models debate a PR, then one inline review posts from your own gh account. **Who it is for:** A developer or reviewer who has a GitHub pull request open and wants a second model to challenge the findings before a human merges. **The problem:** A single reviewer, human or model, can miss bugs or overstate minor issues, and a weak review is easy to skip. **The outcome:** One review with inline comments posted on the PR, with blocking findings separated from non-blocking ones and contested findings shown with both sides' reasoning. ### Steps 1. Run `npx skills add amElnagdy/review-skills` to install the skills into your coding agent. 2. Run `Use $delegate-setup to add two lanes: review-main on claude at high effort and review-debate on codex at high effort.` in your agent, using two different implementers. 3. Run `node /scripts/review-pr.mjs --check` to confirm both reviewers start on this machine. (inferred, check the README) 4. Run `Use $debate-review on https://github.com/owner/repo/pull/123` in your agent, replacing the URL with your PR. 5. Open the PR and read the single review, the P0, P1 and P2 comments, and the summary table. ### Prompt to paste into your agent ```text In the amElnagdy/review-skills repo, run the debate-review skill on using the review-main and review-debate lanes. Report the count of P0, P1 and P2 findings and list any contested findings. Verify the review shows exactly one entry for the current head sha. ``` ### Caveat The reviewers are read-only and cannot edit code, but the debate only adds value when the two lanes use different implementers. Risk, credentials: Reviews and replies post as the account logged in to gh, so the agent acts under your GitHub identity. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/amelnagdy-review-skills/second-opinion-github-pr-review/ ## How to check uncommitted work with a review before opening a PR with Review Skills Repo: [amElnagdy/review-skills](https://github.com/amElnagdy/review-skills) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Reviews the working tree against a base branch and posts nothing to the forge. **Who it is for:** A developer who has finished a change locally and wants a review pass before creating the pull request. **The problem:** Problems found after a PR is open add noise to the forge history and slow down the team. **The outcome:** A printed review of the committed, uncommitted and untracked files, with no comment posted anywhere. ### Steps 1. Run `npx skills add amElnagdy/review-skills` to install the skills. 2. 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. 3. Run `node /scripts/review-pr.mjs --local` from inside the repo to review the working tree. (inferred, check the README) 4. Read the printed findings and fix the blocking ones before you open the PR. ### Prompt to paste into your agent ```text In the amElnagdy/review-skills repo, run the debate-review skill with --local on 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/amelnagdy-review-skills/review-local-changes-before-pr/ ## How to work reviewer threads on a PR until it is merge-ready with Review Skills Repo: [amElnagdy/review-skills](https://github.com/amElnagdy/review-skills) | Difficulty: Advanced | Time: 75 minutes | Basis: From the README Verifies each finding, fixes real blockers, replies, resolves, and re-runs review. **Who it is for:** A developer whose pull request has a stack of review threads from debate-review, Codex, Greptile or other bots and who wants the rounds handled. **The problem:** Going through each reviewer thread by hand, checking the claim, fixing it, and replying takes many rounds. **The outcome:** The threads are answered with evidence and attribution, real blockers are fixed and resolved, and the agent reports when the PR meets the merge gate. ### Steps 1. Install the skills with `npx skills add amElnagdy/review-skills` and make sure gh is logged in to the account that owns the PR. 2. Run `Use $debate-review on https://github.com/owner/repo/pull/123` if the PR has no review yet. 3. Run `Use $babysit-pr on PR 123 until it is ready to merge.` in your agent. 4. Check the agent's report of each thread: which findings were fixed, which were refuted with evidence, and whether the merge gate is met. 5. Merge the PR yourself, since babysit-pr never merges. ### Prompt to paste into your agent ```text In the amElnagdy/review-skills repo, run the babysit-pr skill on PR in until it reports the merge gate is met or it stops. Report each thread with its status and the commit that fixed it. Verify that no thread was resolved without a reply. ``` ### Caveat Reply and resolve are verified live only on GitHub, while Azure DevOps thread harvest is not implemented yet. Risk, credentials: Replies and resolves are posted as your gh account, and the agent pushes fixes to the PR branch. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/amelnagdy-review-skills/babysit-pr-to-merge-ready/ ## How to run a two-model review on a GitLab merge request with Review Skills Repo: [amElnagdy/review-skills](https://github.com/amElnagdy/review-skills) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Posts MR discussions with diff positions from your own glab account. **Who it is for:** A developer or maintainer on a GitLab project, including self-hosted GitLab, who wants a debate-style review on a merge request. **The problem:** Merge requests need a careful review, and a single model review can overlook issues or raise weak ones. **The outcome:** Inline discussions on the merge request with P0, P1 and P2 levels and a summary, posted from your glab account. ### Steps 1. Run `npx skills add amElnagdy/review-skills` and install glab, then log in with glab for your GitLab host. 2. 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. 3. Run `node /scripts/review-pr.mjs --check` to confirm both reviewers start. (inferred, check the README) 4. Run `Use $debate-review on ` using the URL form https://///-/merge_requests/. (inferred, check the README) 5. Read the discussions on the merge request and check the summary table. ### Prompt to paste into your agent ```text In the amElnagdy/review-skills repo, run the debate-review skill on the GitLab merge request . Report the P0, P1 and P2 counts and the first three discussion titles. Verify that the glab account posted one review for the current head sha. ``` ### Caveat GitLab alert colours need GitLab 17.10 or newer, and GitLab reply and resolve through babysit-pr is implemented but not yet verified on a live instance. Risk, credentials: Discussions post under the glab account you are logged in with, so confirm that account before running. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/amelnagdy-review-skills/review-gitlab-merge-request/