skills.rest
tkhieu
tkhieuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Enforce evidence-based verification gates before code review completion.

Updated Aug 27, 2026
Search Tags:#feedback#verification#code-review#pull-request#technical-rigor
One-click install
npx skills add https://github.com/tkhieu/peraichi-coding-agent-starter-kit --skill code-review-tkhieu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/tkhieu/peraichi-coding-agent-starter-kit/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/tkhieu/peraichi-coding-agent-starter-kit --skill code-review-tkhieu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces technical rigor in code review workflows, preventing false completion claims by requiring evidence-based feedback, explicit validation gates, and systematic review via a dedicated code-review subagent.

Core Features & Use Cases

  • Receiving feedback with technical rigor over performative agreement
  • Requesting reviews via the code-reviewer subagent
  • Verification gates that require evidence before any status claims
  • Essential for subagent-driven development, pull requests, and preventing false completion claims

Quick Start

Trigger a post-implementation code-review after each task and run the verification gates before claiming completion. See the protocol docs:

  • references/code-review-reception.md
  • references/requesting-code-review.md
  • references/verification-before-completion.md

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I improve code quality through rigorous review before merging?▼

Code review with technical rigor enforces evidence-based feedback and verification gates before completion. This Skill prevents false completion claims by requiring explicit validation, systematic subagent-driven review, and documented verification that core principles (YAGNI, KISS, DRY) are satisfied before any pull request is merged.

What's the difference between performative code review and evidence-based verification?▼

Evidence-based code review demands concrete verification—test runs, specific technical concerns, measurable compliance checks—rather than surface-level agreement. This Skill mandates verification gates and explicit validation before status claims, ensuring feedback addresses actual technical rigor instead of appearing thorough without substance.

How do I request a formal code review during development?▼

Request code reviews via the dedicated code-reviewer subagent, which enforces systematic, evidence-based feedback on pull requests and post-task implementations. This integrates verification gates and technical validation into your workflow, preventing incomplete or unvalidated work from progressing to completion.

Can I use code review gates in subagent-driven development workflows?▼

Yes. This Skill is designed for subagent-driven development, pull requests, and post-task reviews. It includes verification gates, explicit review protocols, and handling of unclear or technically questionable feedback—all essential for catching incomplete work before claiming completion in agent-assisted development.

When should I run verification before marking a task complete?▼

Run verification gates before any completion claim. This Skill requires evidence-based validation that satisfies core principles (YAGNI, KISS, DRY) and technical rigor standards. Post-implementation code review and pre-merge checks catch gaps that informal review misses, preventing false completion.

What happens when code review feedback is unclear or technically questionable?▼

This Skill handles unclear or technically questionable feedback by enforcing explicit validation and evidence-based standards. The code-reviewer subagent clarifies feedback against concrete technical criteria, ensuring only substantive concerns block completion and preventing subjective or unfounded objections.

Related Skills

Explore More Software Engineering Skills→
duyetduyet
5

quality-gates

Automate quality gate verification for code review and deployment.

Community
Intermediate
vibery-studiovibery-studio
3

code-review

Dispatch a code-reviewer subagent to verify tests, builds, and evidence before completion claims.

Official
Advanced
bobmatnycbobmatnyc
68

pre-merge

Automate pre-merge checks for linting, testing, documentation, security, and CI/CD status.

Community
Advanced
bailynlovebailynlove
1

requesting-code-review

Automate pre-commit code verification with static security scanning and quality gates.

Community
Advanced