cross-review

Delegate code review to a subagent running a specific model. Use ONLY when user explicitly names a model to review changes ("review with opus", "use sonnet to review", "review with gemini"). The root agent reconstructs changes from conversation history and spawns a subagent with the code-review skill using the specified model. Do NOT use for general code review (use code-review skill instead), for reviewing PRs from git history, or when no model is specified by the user.

Zur Installation springen

Repository: EliasOulkadi/shokunin
Letzte Quellaktivität: 19. Mai 2026 um 16:05
Erkannte Sprache von SKILL.md: Englisch
Sterne: 110
Forks: 14

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/EliasOulkadi/shokunin --skill cross-review

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

code-review

spawn_subagent:
  skill: "code-review"
  model: <model from user request>
  prompt: |
    Review the changes below using "code-review" skill.

    CONSTRAINTS:
    - Read-only review. Do NOT edit files.
    - All context is provided below. Read files only if clearly incomplete.
    - Review independently and objectively.

    ## Review Instructions
    {user's review instructions, verbatim}

    ## Changes
    {reconstructed diff, grouped by file}

    ## Additional Context
    {links to related files, tests, type definitions, requirements}

Pattern	Problem	Fix
Using cross-review for general PR review	User did not name a model. cross-review is for explicit model-named delegation only.	Use the standard `code-review` skill instead.
Summarizing or filtering subagent output	The user requested an independent review. Any distortion defeats the purpose.	Relay output verbatim. Add only a 1-line model attribution.
Acting on findings without user approval	The master agent is read-only in this workflow. Fixing issues automatically breaks the delegation contract.	Offer to implement recommendations but wait for user to decide.
Skipping context gathering (Step 2)	Sending only the diff without file context produces shallow reviews that miss type errors and behavioral changes.	Always read final file state and related test/config files before spawning the subagent.
Delegating to the same model the user is already talking to	If user says "review with sonnet" and master agent IS sonnet, this is circular.	Use a different model than the one running the master agent.
Requesting review of unchanged code	cross-review only works on changes made in the current conversation.	If the user wants PR review from git, use the `code-review` skill directly.

Model	Strengths	Best for
Claude Opus 4	Deep reasoning, security analysis, architectural review	Complex refactors, auth code
GPT-5 Codex	Code generation patterns, syntax accuracy	Implementation review, template checking
Gemini 2.5 Pro	Multi-modal, context window size	Large PRs (200+ files), full-repo context
DeepSeek V4	Fast, cost-effective, strong at bug detection	Routine PRs, quick checks

confidence = (models_agreeing / total_models) * evidence_score

evidence_score:
  1.0 = exact line + code excerpt proves the bug
  0.7 = logic analysis suggests probable issue
  0.4 = speculative (pattern matching without code walk)
  0.1 = style preference

name	cross-review
description	Delegate code review to a subagent running a specific model. Use ONLY when user explicitly names a model to review changes ("review with opus", "use sonnet to review", "review with gemini"). The root agent reconstructs changes from conversation history and spawns a subagent with the code-review skill using the specified model. Do NOT use for general code review (use code-review skill instead), for reviewing PRs from git history, or when no model is specified by the user.
triggers	["review with","review using","review via","cross review","different model review"]
negatives	["comprehensive review","zen review","simple review","code review"]
license	MIT
compatibility	opencode
metadata	{"workflow":"review","audience":"developers","version":"1.0.0"}

name	cross-review
description	Delegate code review to a subagent running a specific model. Use ONLY when user explicitly names a model to review changes ("review with opus", "use sonnet to review", "review with gemini"). The root agent reconstructs changes from conversation history and spawns a subagent with the code-review skill using the specified model. Do NOT use for general code review (use code-review skill instead), for reviewing PRs from git history, or when no model is specified by the user.
triggers	["review with","review using","review via","cross review","different model review"]
negatives	["comprehensive review","zen review","simple review","code review"]
license	MIT
compatibility	opencode
metadata	{"workflow":"review","audience":"developers","version":"1.0.0"}

User says	Model ID
opus, claude opus	claude-3-opus
sonnet, claude sonnet	claude-3.5-sonnet
gpt-4, gpt4	gpt-4
gpt-4o	gpt-4o
gemini	gemini-2.0-flash
deepseek	deepseek-chat

cross-review

Installationsoptionen

Quelldateien prüfen

Workflow

Step 1: Parse the user request

Step 2: Gather context from your own changes

Step 3: Spawn the review subagent

Step 4: Relay the result — READ-ONLY, NO ACTIONS

Model Mapping

Error Handling

Anti-Patterns

Model Comparison Methodology

When to use which model

Confidence Scoring

Result Merging Strategy

Handling Conflicts

Checklist

Sources

cross-review

Quellinformationen

Installationsoptionen

Quelldateien prüfen

Mehr aus diesem Repository

Mehr aus diesem Repository

Workflow

Step 1: Parse the user request

Step 2: Gather context from your own changes

Step 3: Spawn the review subagent

Step 4: Relay the result — READ-ONLY, NO ACTIONS

Model Mapping

Error Handling

Anti-Patterns

Model Comparison Methodology

When to use which model

Confidence Scoring

Result Merging Strategy

Handling Conflicts

Checklist

Sources