/review
Gate the work behind a local reviewer panel.
Claude Code
$ npx -y skills add sherifabdlnaby/skills --skill review --agent claude-code
Codex
$ npx skills add sherifabdlnaby/skills --skill review -a codex -y
Cursor
$ npx skills add sherifabdlnaby/skills --skill review -a cursor -y
Gemini CLI
$ npx skills add sherifabdlnaby/skills --skill review -a gemini-cli -y
GitHub Copilot
$ npx skills add sherifabdlnaby/skills --skill review -a github-copilot -y
OpenCode
$ npx skills add sherifabdlnaby/skills --skill review -a opencode -y
Windsurf
$ npx skills add sherifabdlnaby/skills --skill review -a windsurf -y
SKILL.md
review.SKILL.mdname: review description: Gate the work behind a local reviewer panel. license: MIT argument-hint: "[number of reviewers, default 2]" disable-model-invocation: true metadata: author: sherifabdlnaby version: "0.1.0"
review
The task isn't done until it passes a reviewer panel. Run the gate before declaring done.
Panel
`$ARGUMENTS` = reviewer count, default 2:
- `1` → fork reviewer only.
- `2` → 1 independent + 1 fork.
- `N` → N−1 independents with distinct lenses (correctness, functionality, simplification, security, tests) + 1 fork.
Reviewer types:
- **Fork** — an agent forked from this session, carrying the full conversation context. Always on the session model.
- **Independent** — fresh context: give it only the task description and the branch diff vs merge-base.
Cross-model: If you are Claude, and have access to Open AI Model (like in Cursor), then prefer cross-model reviewers as long as they're not a weaker model. For example, Opus 4.8 <-> GPT 5.5
Gate
1. Run the panel in parallel. 2. Triage findings: fix the real ones; reject with a stated reason (you have context reviewers lack), or escalate to user. 3. One re-review round, of the fixes only. 4. Gate opens. Escalate, contested or rejected findings go in the final summary.
🍣 Hand-rolled AI Skills distilled from my everyday experience. Git & Mise (...and others).
Other skills on skills.
cicd-fy
Use when setting up, shaping, or auditing a project's CI/CD: a build/test/scan pipeline, a release pipeline, or publishing an…
coding
The user's coding and docs conventions and taste. Load FIRST, at the start of any task that touches code or docs.
git
Load when planning or about to git commit, branch, push, rebase, resolve a merge conflict, open PR, stack PRs (even when gh-stack…
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about review.
- Which coding agents can use review?
- review installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

