skills.rest
nguyenvanlinh1902
nguyenvanlinh1902COMMUNITY
Explore all skills by this author →
GitHub

code-review

Coordinate subagent-based code reviews with evidence verification gates.

Updated Dec 16, 2025
Search Tags:#workflow#verification#subagent#gates#quality-assurance#code-review
One-click install
npx skills add https://github.com/nguyenvanlinh1902/trackingSolar --skill code-review-nguyenvanlinh1902
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nguyenvanlinh1902/trackingSolar/tree/main/.opencode/skill/code-review
Command: npx skills add https://github.com/nguyenvanlinh1902/trackingSolar --skill code-review-nguyenvanlinh1902

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews are often inconsistent and lack traceable verification. This Skill provides a structured, rules-driven protocol to perform, document, and validate reviews with clear gates and references.

Core Features & Use Cases

  • Enforces an evidence-first verification model for code changes
  • Supports after-each-task and pre-merge reviews via a code-reviewer subagent
  • Centralizes references and protocols to prevent scope drift and rework

Quick Start

Dispatch a review after completing a task and have the code-reviewer validate changes with evidence before proceeding.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce traceable verification during code reviews?▼

Evidence-based code reviews require a structured protocol that validates changes through verification gates before merges. This approach coordinates subagent-based reviews to guarantee traceability and accountability for each task.

What is the best way to automate pre-merge code reviews?▼

Automating pre-merge code reviews is best achieved by dispatching a code-reviewer subagent to validate changes with evidence. This prevents scope drift and ensures evidence-based completion before a merge occurs.

How do I prevent scope drift during software verification?▼

Preventing scope drift during software verification involves centralizing references and protocols within a rules-driven code review process. This maintains accountability and reduces rework by enforcing structured gates.

Can I use subagent-based reviews after each development task?▼

Yes, subagent-based reviews can be dispatched after completing each individual development task. The code-reviewer validates the changes with evidence before allowing the workflow to proceed to the next step.

Does artifact-backed code review work without external dependencies?▼

Artifact-backed code review works without external dependencies, relying instead on internal structured references and verification gates. This self-contained design ensures traceable validation without requiring additional integrations.

Related Skills

Explore More Software Engineering Skills→
seanGSISGseanGSISG
3

requesting-code-review

Dispatch a code-reviewer subagent with Git SHAs and implementation details.

Community
Basic
mchien15mchien15

code-review

Automate evidence-based code reviews with scout-based edge-case detection.

Community
Advanced
brabos-aibrabos-ai
8

add-subagent-driven-development

Dispatch independent subagents for iterative development tasks with enforced code reviews.

Official
Advanced
skywatch-bskyskywatch-bsky
6

reviewing-osprey-rules

Validate Osprey SML rule sets via CLI dry-runs and logic checks.

Official
Advanced