code-review

Review code for technical correctness and edge cases before pull requests.

Updated Feb 11, 2026

Search Tags:#quality assurance #code review #pull request #edge cases #verification #scouting

Ready to run

npx skills add https://github.com/IoT-VN/tuya-energy-dashboard --skill code-review-iot-vn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/IoT-VN/tuya-energy-dashboard/tree/main/.opencode/skills/code-review
Command: npx skills add https://github.com/IoT-VN/tuya-energy-dashboard --skill code-review-iot-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures code quality and correctness by enforcing technical rigor, verifying claims, and proactively identifying edge cases before code is merged or work is claimed as complete.

Core Features & Use Cases

Technical Rigor: Emphasizes principles like YAGNI and KISS, prioritizing correctness over performative responses.
Edge Case Scouting: Utilizes a scout agent to proactively find potential issues after implementation but before review.
Verification Gates: Mandates evidence-based verification before any completion claims are made.
Use Case: Before submitting a Pull Request for a new feature, you can use this Skill to scout for edge cases, request a formal code review from a sub-agent, and ensure all tests pass, guaranteeing a higher quality submission.

Quick Start

Use the code-review skill to scout edge cases for the recent changes in the main branch.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I verify code quality and detect edge cases before a pull request?▼

Code review before a pull request requires enforcing technical correctness and proactively scouting edge cases. This verification gate ensures evidence-based completion claims are validated against YAGNI, KISS, and DRY principles prior to task sign-off.

What is edge case scouting in software verification?▼

Edge case scouting is a proactive verification step using sub-agents to find potential issues after implementation but before formal review. It ensures technical correctness by identifying boundary conditions prior to a pull request sign-off.

How do I enforce YAGNI and KISS principles during a code review?▼

Enforce YAGNI and KISS principles during code review by prioritizing technical correctness over performative responses. The review process mandates adherence to these principles to ensure the implementation remains simple and necessary.

Can I use sub-agents to automate pull request verification?▼

Yes, you can use sub-agents to automate pull request verification by deploying a scout agent to proactively find edge cases. This sub-agent conducts formal reviews and mandates evidence-based verification before task completion is claimed.

What are the limitations of automated code review scouting?▼

Automated code review scouting limitations center on its dependency on evidence-based verification; it cannot claim completion without proof. It enforces technical rigor but requires strict adherence to YAGNI, KISS, and DRY principles to avoid performative responses.