Writing Style
umputun/cc-thingz
A skill your agent uses for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages.
Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.
Install Debate Review
$ npx skills add amElnagdy/review-skills --skill debate-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install amElnagdy/review-skills debate-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/amElnagdy/review-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/debate-review .claude/skills/debate-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debate-review" agent skill from https://github.com/amElnagdy/review-skills/tree/master/skills/debate-review into .claude/skills/debate-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debate-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/amElnagdy/review-skills/tree/master/skills/debate-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add amElnagdy/review-skills --skill debate-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install amElnagdy/review-skills debate-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amElnagdy/review-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/debate-review .agents/skills/debate-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debate-review" agent skill from https://github.com/amElnagdy/review-skills/tree/master/skills/debate-review into .agents/skills/debate-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debate-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amElnagdy/review-skills --skill debate-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install amElnagdy/review-skills debate-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amElnagdy/review-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/debate-review .cursor/skills/debate-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debate-review" agent skill from https://github.com/amElnagdy/review-skills/tree/master/skills/debate-review into .cursor/skills/debate-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debate-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/amElnagdy/review-skills.git --path skills/debate-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add amElnagdy/review-skills --skill debate-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install amElnagdy/review-skills debate-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amElnagdy/review-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/debate-review .gemini/skills/debate-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debate-review" agent skill from https://github.com/amElnagdy/review-skills/tree/master/skills/debate-review into .gemini/skills/debate-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debate-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install amElnagdy/review-skills debate-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add amElnagdy/review-skills --skill debate-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/amElnagdy/review-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/debate-review .github/skills/debate-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debate-review" agent skill from https://github.com/amElnagdy/review-skills/tree/master/skills/debate-review into .github/skills/debate-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debate-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amElnagdy/review-skills --skill debate-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install amElnagdy/review-skills debate-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amElnagdy/review-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/debate-review .opencode/skills/debate-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debate-review" agent skill from https://github.com/amElnagdy/review-skills/tree/master/skills/debate-review into .opencode/skills/debate-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debate-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debate-review- GitHub stars
- 132
- Used in
- 2 other repos
- Token cost
- ~1.1k tokens
- SKILL.md length
- 549 words
- Files
- 14 (incl. scripts, references, assets)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.
- Any PR/MR review request
- SKILL.md covers Run it, After it posts and Artifacts
- Runs JavaScript scripts from its folder; calls node and az
- A local review before a PR exists
What it does
Debate Review is an agent skill from amElnagdy/review-skills. Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed. Use for any PR/MR review request, or a local review before a PR exists.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including scripts, reference files and assets (for example `assets/prompts/review-debate.md`, `assets/prompts/review-main.md` and `assets/prompts/review-rebuttal.md`). Compatibility notes: Requires Node 18+, Git 2.31+ for Azure DevOps, gh (GitHub), glab (GitLab) or az (Azure DevOps) authenticated, and delegate-skills installed for the…
It sits in Development, covering Technical documentation. It works with Azure DevOps, GitHub and GitLab. The repository describes itself as: Two-model debate review of PRs and MRs, plus a babysitter that works the review rounds. Skills for any coding agent. The licence is MIT.
When your agent uses it
- Any PR/MR review request
- A local review before a PR exists
Example prompts
- “/debate-review”
Requirements
- Node.js
- Compatibility (from SKILL.md): Requires Node 18+, Git 2.31+ for Azure DevOps, `gh` (GitHub), `glab` (GitLab) or `az` (Azure DevOps) authenticated, and delegate-skills installed for the main/debate lanes.
What it can do on your machine
Read from SKILL.md and the folder at commit 3cfce39. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 8 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
nodeaz
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use az, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires Node 18+, Git 2.31+ for Azure DevOps, `gh` (GitHub), `glab` (GitLab) or `az` (Azure DevOps) authenticated, and delegate-skills installed for the main/debate lanes.
From compatibility in the SKILL.md frontmatter.
Context cost
Debate Review loads about 1.1k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 549 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from amElnagdy/review-skills at commit 3cfce39, republished under its MIT licence (© amElnagdy). 549 words, ~1,066 tokens.
Download SKILL.mdSave it as
.claude/skills/debate-review/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.- name
- debate-review
- description
- Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed. Use for any PR/MR review request, or a local review before a PR exists.
- compatibility
- Requires Node 18+, Git 2.31+ for Azure DevOps, `gh` (GitHub), `glab` (GitLab) or `az` (Azure DevOps) authenticated, and delegate-skills installed for the main/debate lanes.
- license
- MIT
- metadata.version
- 0.2.0
debate-review
Two models argue before anything is posted. A main reviewer finds issues. A debate reviewer tries to
knock them down and may add its own. The main reviewer then makes the final call, and one review with
inline comments lands on the PR or MR. It posts from the user's own gh, glab or az account as a
non-approval review or comment. It never approves and never requests changes.
You are the orchestrator. You run one command and relay the result. You do not review the diff yourself, and you do not touch the PR.
Run it
node "<skill-dir>/scripts/review-pr.mjs" --local [--base <ref>]
node "<skill-dir>/scripts/review-pr.mjs" <pr-url | number> [--dry-run]- If the user wants a review and there is no PR/MR URL, run
--localfrom the repo (or--repo-dir). Do not invent a URL. Relay stdout.--localnever talks to a forge and rejects non-UTF-8 Git paths rather than decoding them lossily. <pr-url>is a GitHub/pull/N, GitLab/-/merge_requests/N, or Azure DevOps/_git/<repo>/pullrequest/NURL (dev.azure.comor the legacy*.visualstudio.com). A bare number resolves against the cwd'sorigin, including Azure DevOps https andssh.dev.azure.com:v3/remotes.--dry-runprints a live PR review instead of posting it. It does not combine with--local.- Azure DevOps needs
azlogged in (az login) with access to the project. No extension is required, the script talks to the REST API throughaz rest. A review there is N inline comment threads plus one closed summary thread, since Azure DevOps has no single review object; the alert blockquotes render as plain quotes, which still read. - The reviewers are two delegate-skills lanes,
review-mainandreview-debate. If either is missing the script says so. Add them withdelegate-setup. Pick two different implementers, since the debate is only worth something when the second model doesn't share the first one's blind spots (mainclaudeorgrok, debatecodexat high effort is a good pair). For a one-off, pass--main <implementer>or--debate <implementer>. Only implementers whose relay has--read-onlyare accepted. These two lanes belong to the reviewer. Don't point them at a lane you use for other work, such as a plan-debate lane. --checkstarts each reviewer on a one-line read-only brief and printsokorFAILwith the reason per role, exit1on any failure. Run it once on every machine after setting up the lanes; it catches a reviewer that is not installed, not signed in, out of quota, or refused by its sandbox before a PR waits on it.- Exit code
3means this head sha already has a debate-review. Re-run with--forceto post again. - A run takes minutes, since it is two or three implementer sessions back to back. Run it in the background and report the printed URL when it finishes. Don't poll tightly.
Show full SKILL.md (101 more words)Show less
All flags: --help. Contracts: references/schema.md. What gets posted:
references/comment-format.md. The reviewer briefs live in assets/prompts/
and the script fills them in; you don't need to read them.
After it posts
Each posted comment carries a <!-- debate-review:<id> status=... --> marker. babysit-pr handles
GitHub and GitLab rounds (verify, fix blockers, reply, resolve). It cannot harvest Azure DevOps yet,
so relay Azure findings directly to the user. Don't act on the findings yourself unless asked.
Artifacts
~/.cache/debate-review/<owner>__<repo>/<N>/<head>/ holds run.json (all three documents, timings,
what was posted) plus main/, debate/, and final/, each with the brief sent and the relay's
result.json.
--local writes under ~/.cache/debate-review/local/<repo>/<branch>/<head>/ instead.
© amElnagdy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 13 other files (scripts, references, assets) in skills/debate-review of amElnagdy/review-skills.
- SKILL.md
- assets/prompts/review-debate.md
- assets/prompts/review-main.md
- assets/prompts/review-rebuttal.md
- references/comment-format.md
- references/schema.md
- scripts/lib/diff.mjs
- scripts/lib/dispatch.mjs
- scripts/lib/forge.mjs
- scripts/lib/local.mjs
- scripts/lib/render.mjs
- scripts/lib/shell.mjs
- scripts/lib/validate.mjs
- scripts/review-pr.mjs
Open the folder on GitHubat commit 3cfce39
Used in 2 other repositories
We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in amElnagdy/review-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Debate Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debate Review this skillamElnagdy/review-skills | 132 | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Writing Styleumputun/cc-thingz | 485 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Qodo PR Resolversbusso/claudeclaw | 194 | — | ~4k | Automated safety check: Pass | MIT | |
| Researching With Deepwikiaiskillstore/marketplace | 433 | — | ~1.2k | Automated safety check: Pass | None | |
| Promotion Branches E2E Testhardisgroupcom/sfdx-hardis | 403 | — | ~11k | Automated safety check: Notes | AGPL-3.0 | |
| Authoring GitHub Workflowsdotnet/skills | 5.6k | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Qodo PR Resolver
sbusso/claudeclaw
Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)
Researching With Deepwiki
aiskillstore/marketplace
Research GitHub, GitLab, and Bitbucket repositories using DeepWiki MCP server.
Promotion Branches E2E Test
hardisgroupcom/sfdx-hardis
Runs a full end-to-end test of sfdx-hardis promotion branches and backpromote against real Salesforce orgs and a throwaway repository, then writes a report.
- Official
Authoring GitHub Workflows
dotnet/skills
Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.
PR
kdlbs/kandev
Create a PR from a committed and pushed branch after task-defined checks pass.
More from amElnagdy/review-skills
Babysit PR
amElnagdy/review-skills
Babysit a pull request through its bot review rounds: verify, fix, reply, resolve.
Related
Works with
Categories
Questions about Debate Review
What does Debate Review do?
Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed. Debate Review is an agent skill from amElnagdy/review-skills. Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.
When should I use Debate Review?
Debate Review fits situations like: any PR/MR review request; A local review before a PR exists.
How do I install Debate Review in Claude Code?
Run `npx skills add amElnagdy/review-skills --skill debate-review -a claude-code`. Or copy the skill folder (skills/debate-review in amElnagdy/review-skills) into .claude/skills/debate-review in your project. Claude Code loads it when a task matches its description.
How do I install Debate Review in Codex?
Run `npx skills add amElnagdy/review-skills --skill debate-review -a codex`. Or copy the skill folder (skills/debate-review in amElnagdy/review-skills) into .agents/skills/debate-review in your project. Codex loads it when a task matches its description.
Can I use Debate Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amElnagdy/review-skills --skill debate-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debate-review, .gemini/skills/debate-review, .github/skills/debate-review and .opencode/skills/debate-review in your project.
What does Debate Review need to run?
Going by SKILL.md and its folder, Debate Review needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and az). Our summary lists: Node.js. Compatibility (from SKILL.md): Requires Node 18+, Git 2.31+ for Azure DevOps, `gh` (GitHub), `glab` (GitLab) or `az` (Azure DevOps) authenticated, and delegate-skills installed for the main/debate lanes..
Does Debate Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debate Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Debate Review use?
Debate Review is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debate Review use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.
What are the alternatives to Debate Review?
Skills that share tags, products or a category with Debate Review: Writing Style (umputun/cc-thingz, 485 stars), Qodo PR Resolver (sbusso/claudeclaw, 194 stars), Researching With Deepwiki (aiskillstore/marketplace, 433 stars) and Promotion Branches E2E Test (hardisgroupcom/sfdx-hardis, 403 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debate Review?
amElnagdy (a GitHub user) maintains it in amElnagdy/review-skills, which has 132 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: amElnagdy/review-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.