skills.rest
lv7dev
lv7devCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Enforce technical rigor in code reviews with verification gates.

Updated Feb 3, 2026
Search Tags:#verification#code-quality#subagent#code-review#pull-request
One-click install
npx skills add https://github.com/lv7dev/shop_v2 --skill code-review-lv7dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/lv7dev/shop_v2/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/lv7dev/shop_v2 --skill code-review-lv7dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews can be slow, error-prone, and dominated by social cues; this skill enforces technical rigor, prevents performative agreement, and ensures verification before status claims.

Core Features & Use Cases

  • Receiving feedback with technical rigor over performative agreement.
  • Requesting reviews via a code-reviewer subagent.
  • Verification gates before completion, PRs, or status claims.
  • Use cases: after each subtask, before merging to main, or when fixing complex bugs.

Quick Start

Trigger a code-review pass after finishing a task. Dispatch the code-reviewer subagent with WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to obtain an early, structured review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce technical rigor in automated code reviews?▼

To enforce technical rigor in code reviews, apply verification gates before any completion status or pull request merge. This prevents performative agreement by requiring evidence-based feedback validation for subagent-driven development tasks.

What is a verification gate before merging a pull request?▼

A verification gate before merging a pull request is a mandatory check that confirms feedback has been technically validated. It blocks status claims and merges until code-review evidence is fully verified.

How do I request a code review via a subagent?▼

To request a code review via a subagent, dispatch the code-reviewer with parameters like WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to obtain structured, early feedback.

How do I stop performative agreement in subagent-driven development?▼

To stop performative agreement in subagent-driven development, enforce receiving feedback with technical rigor. This ensures all code review assertions are evidence-based rather than socially driven.

When should I trigger an evidence-based code review pass?▼

Trigger an evidence-based code review pass after finishing each subtask, before merging to main, or when fixing complex bugs. This ensures structured validation occurs exactly when feedback is needed.

Does subagent code review work for fixing complex bugs?▼

Subagent code review works for fixing complex bugs by dispatching the code-reviewer with the implementation plan and SHAs. This provides structured, verified feedback before declaring the bug fix complete.

Related Skills

Explore More Software Engineering Skills→
marcusfelixmarcusfelix

requesting-code-review

Dispatch a code-reviewer subagent to analyze git changes against requirements.

Community
Intermediate
fredrikaverpilfredrikaverpil
253

code-review

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

Community
Basic
hanibalskhanibalsk
3

subagent-driven-development

Execute implementation plans by dispatching fresh subagents with code reviews between tasks.

Community
Advanced
winsorllcwinsorllc

code-review

Execute linters, static analysis, and security scanners on code.

Community
Intermediate