code-review

Review code changes through multi-stage verification gates and edge case scouting.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/toanalien/ezdevsecops --skill code-review-toanalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/toanalien/ezdevsecops/tree/main/.opencode/skills/code-review
Command: npx skills add https://github.com/toanalien/ezdevsecops --skill code-review-toanalien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures code quality through rigorous, evidence-based review processes, preventing the introduction of bugs and ensuring task completion claims are valid.

Core Features & Use Cases

  • Technical Rigor: Enforces principles like YAGNI and KISS, prioritizing correctness over performative responses.
  • Verification Gates: Mandates running verification commands before any completion claim.
  • Edge Case Scouting: Proactively identifies potential issues using a scout skill before formal review.
  • Use Case: Before merging a new feature, use this Skill to scout for edge cases, request a formal code review, and verify all tests pass, ensuring a high-quality, robust submission.

Quick Start

Use the code-review skill to scout edge cases for the recent changes and then request a formal review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I verify edge cases before creating a pull request?

Edge case detection before a pull request uses a scouting process to proactively identify potential issues. This code review approach enforces technical correctness and validates completion claims using evidence-based verification gates before submission.

What is an evidence-based verification gate in code review?

An evidence-based verification gate is a mandatory checkpoint requiring verification commands to run successfully before claiming task completion. It enforces principles like YAGNI and KISS, prioritizing correctness over performative responses during the code review process.

How do I perform a multi-stage code review after feature implementation?

Multi-stage code review after feature implementation involves scouting for edge cases, requesting a formal review, and verifying all tests pass. This ensures high-quality submissions by enforcing technical rigor and validating task completion claims through evidence.

Does this code review process enforce YAGNI and KISS principles?

Yes, this code review process enforces YAGNI and KISS principles to prioritize correctness over performative responses. It mandates running verification commands before any completion claim, ensuring technical rigor and preventing the introduction of bugs.

When do I need a formal code review for task completion validation?

You need a formal code review for task completion validation when ensuring code quality and preventing bugs before merging. It enforces evidence-based verification gates, requiring successful verification command execution before any claims of completion are accepted.