code-review

Enforce verification gates and evidence-based claims in code review processes.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/chef0111/physthink --skill code-review-chef0111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/chef0111/physthink/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/chef0111/physthink --skill code-review-chef0111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenges of ensuring technical rigor in code reviews, preventing performative agreement, and establishing clear verification gates before claiming completion. It aims to improve code quality and reduce errors by enforcing systematic review processes.

Core Features & Use Cases

  • Technical Rigor: Emphasizes verifying feedback and code correctness over social comfort or blind agreement.
  • Systematic Review: Integrates with a code-reviewer subagent for structured feedback.
  • Verification Gates: Mandates evidence-based claims, preventing premature declarations of success.
  • Use Case: When a developer receives feedback on a pull request, this Skill ensures they technically evaluate each comment, request a formal review if needed, and only then confirm that tests pass and the code is ready for merging.

Quick Start

Use the code-review skill to ensure all feedback on the latest commit is technically verified 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 technical rigor during a code review?

To enforce technical rigor in a code review, prioritize verification over performative agreement by systematically evaluating feedback, verifying claims with concrete evidence, and applying strict completion gates before updating pull request statuses.

What is performative agreement in code review and how do I prevent it?

Performative agreement in code review happens when developers accept feedback for social comfort rather than technical accuracy. Prevent it by mandating evidence-based verification of all code claims and systematically evaluating each comment before confirming completion.

How do I verify pull request feedback before claiming completion?

You verify pull request feedback by requesting a formal review through a dedicated subagent, technically evaluating each returned comment, and demanding evidence. Only confirm tests pass and the code is ready after this systematic verification gate is cleared.

How do I set up verification gates for a pull request?

You set up verification gates by integrating a subagent for structured feedback, requiring evidence for all technical claims, and mandating a systematic review pass. This prevents premature declarations of success before the code is ready for merging.

When do I need a systematic code review process?

You need a systematic code review process when you receive feedback on a commit and must ensure technical correctness before merging. It is essential for preventing errors, enforcing technical rigor, and reducing blind agreement during quality assurance.