en un clic
review
Gate the work behind a local reviewer panel.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Menu
Gate the work behind a local reviewer panel.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | 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"} |
The task isn't done until it passes a reviewer panel. Run the gate before declaring done.
$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:
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
A relentless interview that asks every frontier question at once, round by round. (Sherif's version).
Load when creating a new skill, scaffolding a SKILL.md, adding a reference page to a skill, writing or tuning a skill's description, or restyling/auditing an existing skill. Carries the authoring patterns (progressive disclosure, router, voice, triggering) a skill is shaped with.
Load when planning or about to git commit, branch, push, rebase, resolve a merge conflict, open PR, stack PR, or write/update the description of a Pull Request (PR / stacked diff), respond to review comments, review a PR, or watch/babysit a PR's CI. Carries the user's git conventions and style you are expected to match. Load as early as possible, the moment git or GitHub work is anywhere in the chat's future.
The user's coding and docs conventions and taste. Load FIRST, at the start of any task that touches code or docs.
Use when setting up, shaping, or auditing a project's CI/CD: a build/test/scan pipeline, a release pipeline, or publishing an artifact (container image, binary, bundle) with signing/attestation. Optionally use the skill to transform a repo's CI/CD to the recommended shape, aka (cicd-fy).
/afk, but local-only and conservative.