workbench-code-review
Workbench Code Review
Use this skill for reviewing code, diffs, task plans, live workflow changes, and implementation evidence before merge or closure.
Review Stance
- Findings first. Do not lead with praise or a broad summary.
- Order findings by severity and user impact.
- Tie every finding to a file, command, issue/comment ID, run ID, or observable behavior.
- Prefer concrete repro or blast-radius evidence over style opinions.
- If no issues are found, say that clearly and name remaining test gaps.
Severity
P0: security, data loss, irreversible action, or broken primary workflow.P1: likely user-facing regression or unsafe automation.P2: correctness gap, missing edge case, or weak verification.P3: maintainability, clarity, or low-risk cleanup.
More from fearvox/multica-ultimate-workbench
workbench-design-docs
Product design, technical design documents, user-facing copy, specs, diagrams, and handoff documentation.
7workbench-token-context-discipline
Compact context, cache-aware execution, scoped evidence reads, and role-specific skill attachment discipline.
6workbench-gsd-tasking
Owner-scoped task decomposition with gates, rollback, verification commands, and smoke tests.
6workbench-memory-synthesis
Durable memory, session summaries, decision logs, issue closeout synthesis, and compact handoffs.
6workbench-implementation
Minimal-patch implementation, ops changes, scripts, automation specs, and local repository edits.
6workbench-research
Evidence-first research, architecture discovery, vendor documentation review, benchmark reading, and unknown-system analysis.
6