sk-code-review

code-review Mode - Stack-Agnostic Findings-First Review

Universal findings-first review baseline paired with sk-code surface standards evidence for the detected code surface.

1. WHEN TO USE

Activation Triggers

Use the code-review mode (of the sk-code family) when:

• A user asks for code review, PR review, quality gate, or merge readiness.
• A workflow dispatches @review for pre-commit or gate validation.
• A user requests security/correctness risk analysis before merge.
• A user wants severity-ranked findings with file:line evidence.

Keyword Triggers

review, code review, pr review, audit, security review, quality gate, request changes, findings, blocking issues, merge readiness

Use Cases

1. Review-only pass: findings-first output with no code edits.
2. Gate validation: score + pass/fail recommendation for orchestrated workflows.
3. Focused risk pass: security, concurrency, correctness, or removal-focused review.

When NOT to Use

• Feature implementation without review intent; use the surface skill (code-webflow / code-opencode).
• Pure documentation editing where code behavior is not being assessed.
• Git-only workflow tasks (branching, rebasing, commit hygiene) without code-quality evaluation intent.
• Applying review fixes after findings are accepted; use the surface skill (code-webflow / code-opencode).
• Author-side quality gates before review; use code-quality.
• Root-cause debugging; use the surface's workflow-debug.md doctrine.
• Verification evidence collection; use the surface's workflow-verify.md doctrine.

---

2. SMART ROUTING

Primary Detection Signal

Review behavior follows a baseline+surface-evidence model:

• Baseline (always): the code-review mode (of the sk-code family) findings-first doctrine.
• Surface standards evidence (when available): sk-code detected surface resources.
• Unknown surfaces: review against baseline security/correctness only and disclose uncertainty.