Help us improve
Share bugs, ideas, or general feedback.
From copilot
Run a Copilot review that challenges the implementation approach and design choices
npx claudepluginhub wagnersza/copilot-plugin-cc --plugin copilotHow this command is triggered — by the user, by Claude, or both
Slash command
/copilot:adversarial-review [--wait|--background] [--base <ref>] [--scope auto|working-tree|branch] [focus ...]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Run an adversarial Copilot review through the shared plugin runtime. Position it as a challenge review that questions the chosen implementation, design choices, tradeoffs, and assumptions. It is not just a stricter pass over implementation defects. Raw slash-command arguments: `$ARGUMENTS` Core constraint: - This command is review-only. - Do not fix issues, apply patches, or suggest that you are about to make changes. - Your only job is to run the review and return Copilot's output verbatim to the user. - Keep the framing focused on whether the current approach is the right one, what assu...
/adversarial-reviewRuns adversarial Codex review challenging implementation approach, design choices, tradeoffs, and assumptions on git-scoped codebase. Supports --wait, --background, --base <ref>, --scope, focus args.
/adversarial-reviewRun a Gemini review that challenges the implementation approach and design choices
/adversarial-reviewRun a Qwen review that challenges the implementation approach and design choices
/adversarialRuns adversarial code review on uncommitted changes: challenges design decisions, probes assumptions, identifies failure modes, questions trade-offs with severity-rated recommendations.
/reviewRuns Codex adversarial review on current diff, writing findings and proposed fix patches to reviews/ directory. Read-only in v1.
/sc-adversarial-reviewRuns multi-model adversarial review using Codex, Gemini, and Claude on files, directories, staged changes, branches, or PRs for diverse critiques.
Share bugs, ideas, or general feedback.
Run an adversarial Copilot review through the shared plugin runtime. Position it as a challenge review that questions the chosen implementation, design choices, tradeoffs, and assumptions. It is not just a stricter pass over implementation defects.
Raw slash-command arguments:
$ARGUMENTS
Core constraint:
Execution mode rules:
--wait, do not ask. Run in the foreground.--background, do not ask. Run in a Claude background task.git status --short --untracked-files=all.git diff --shortstat --cached and git diff --shortstat.git diff --shortstat <base>...HEAD.git diff --shortstat is empty.AskUserQuestion exactly once with two options, putting the recommended option first and suffixing its label with (Recommended):
Wait for resultsRun in backgroundArgument handling:
--wait or --background yourself.--wait and --background, but Claude Code's Bash(..., run_in_background: true) is what actually detaches the run./copilot:adversarial-review uses the same review target selection as /copilot:review.--base <ref>.--scope staged or --scope unstaged./copilot:review, it can still take extra focus text after the flags.Foreground flow:
node "${CLAUDE_PLUGIN_ROOT}/scripts/copilot-companion.mjs" adversarial-review "$ARGUMENTS"
Background flow:
Bash in the background:Bash({
command: `node "${CLAUDE_PLUGIN_ROOT}/scripts/copilot-companion.mjs" adversarial-review "$ARGUMENTS"`,
description: "Copilot adversarial review",
run_in_background: true
})
BashOutput or wait for completion in this turn./copilot:status for progress."