code-review

Evaluate code review feedback with subagent checks and evidence-based verification gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams enforce technical rigor in code reviews, ensuring feedback is evaluated, not just acknowledged, and preventing premature completion claims.

Core Features & Use Cases

  • Receiving feedback with structured evaluation and pushback when needed.
  • Invoking a code-reviewer subagent for independent verification on major changes or PRs.
  • Enforcing verification gates before status claims, merges, or deployments.

Quick Start

When you receive code changes, invoke the code-review workflow to verify feedback, trigger a reviewer check, and apply evidence-based validation 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 evidence-based code reviews before merging a pull request?

Evidence-based code reviews enforce technical correctness by invoking a code-reviewer subagent for independent verification and requiring traceable verification gates before pull request merges. This prevents premature completion claims and performative agreements on major features.

What is the best way to evaluate code review feedback to avoid performative agreements?

Evaluating code review feedback involves structured evaluation and pushback when needed, ensuring technical correctness is verified rather than just acknowledged. A subagent-based review process applies evidence-based validation to check feedback against actual code changes.

How do I gate deployment with verifiable evidence from a code review?

Gating deployment with verifiable evidence requires applying verification gates before status claims or merges, utilizing subagent-based reviews to generate traceable validation. This ensures merge points satisfy requirements for evidence-based responses before proceeding.

When should I initiate a code-reviewer check during the engineering process?

Initiate a code-reviewer check across tasks, major features, and merge points to ensure technical rigor. The code review workflow triggers independent verification on major changes or pull requests, enforcing validation before completion claims.

Can I use subagent-based reviews for independent verification on major changes?

Subagent-based reviews provide independent verification for major changes by evaluating code review feedback and applying traceable verification gates. This approach ensures technical correctness and prevents performative agreements during the engineering process.