code-review

Enforce evidence-based code review and verification gates before completion.

Updated Jun 16, 2025
One-click install
npx skills add https://github.com/Stonelukas/Mouse-on-Numpad --skill code-review-stonelukas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Stonelukas/Mouse-on-Numpad/tree/main/.opencode/skill/code-review
Command: npx skills add https://github.com/Stonelukas/Mouse-on-Numpad --skill code-review-stonelukas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enforces rigorous, evidence-based code reviews to prevent unverified completion claims and biased feedback.

Core Features & Use Cases

  • Receiving Feedback Protocol: evaluates and responds to feedback with structured verification and disciplined questioning.
  • Requesting Reviews: coordinates code-reviewer subagent checks after each task or major feature and before merges.
  • Verification Gates: guarantees tests, builds, and requirements are validated before declaring completion or progress.
  • The skill uses frontmatter-driven guidance plus references to standardized handling to maintain technical rigor.

Quick Start

To start an evidence-based review session, articulate your feedback with exact requirements and request a formal code-review from the subagent.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce evidence-based code reviews to prevent unverified completion claims?

Evidence-based code reviews prevent unverified completion claims by enforcing verification gates that validate tests, builds, and requirements before declaring progress. This ensures structured feedback and traceable verification across subagent workflows.

How do I coordinate a code-reviewer subagent to check my pull request before a merge?

To coordinate a code-reviewer subagent for a pull request, articulate your feedback with exact requirements and request a formal code review. The subagent applies verification gates to catch issues early before merges.

What is a verification gate in a code review workflow?

A verification gate in a code review workflow is a formal checkpoint that guarantees tests, builds, and requirements are validated before completion. It enforces disciplined handoffs and structured feedback across subagent tasks.

How do I handle receiving feedback during a formal code review session?

Handling feedback during a code review requires a receiving protocol that evaluates responses with structured verification and disciplined questioning. This mitigates biased feedback and maintains technical rigor.

Can I use this code review process for any coding task or only large features?

You can use this code review process for any coding task. The skill applies verification gates and subagent checks after each task or major feature to catch issues early across all coding workflows.

What are the limitations of automated code review for quality assurance?

A limitation of automated code review is its reliance on frontmatter-driven guidance and standardized references. It requires exact requirements and disciplined questioning to successfully mitigate biased feedback and prevent unverified claims.