skills.rest
Khoatran1999
Khoatran1999COMMUNITY
Explore all skills by this author →
GitHub

code-review

Evaluate code changes against evidence with verification gates before merging.

Updated Jan 24, 2026
Search Tags:#verification#evidence#code-review#software-engineering#quality-control#pull-request
One-click install
npx skills add https://github.com/Khoatran1999/aquarium-commerce --skill code-review-khoatran1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Khoatran1999/aquarium-commerce/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/Khoatran1999/aquarium-commerce --skill code-review-khoatran1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code review helps teams enforce technical rigor by evaluating changes against evidence rather than social agreement.

Core Features & Use Cases

  • Receiving Feedback Protocol: Evaluate feedback with technical reasoning, verify against the codebase, and implement changes iteratively with testing.
  • Requesting Reviews: Dispatch a code-reviewer subagent after tasks or major features to catch issues early.
  • Verification Gates: Enforce evidence-based completion before claims of success or readiness for merge.

Quick Start

Summarize the changes, request a code review, and run verification before claiming completion.

Frequently Asked Questions about code-review

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

FAQPage Schema
What is evidence-based code review and how does it work?▼

Request a code review by dispatching a code-reviewer subagent after completing tasks or major features. Summarize the changes, run the review, and execute verification gates before claiming completion.

When should I request a pull request review in a subagent-driven workflow?▼

Request a pull request review after completing tasks or major features and before merging to main. This timing catches issues early and enforces evidence-based completion before any success claims.

How do I handle code review feedback for technical rigor?▼

Handle code review feedback by evaluating it with technical reasoning, verifying suggestions against the codebase, and implementing changes iteratively with thorough testing before merging.

Do I need verification gates before claiming a pull request is ready to merge?▼

Yes, verification gates are required before claiming a pull request is ready to merge. They enforce evidence-based completion, ensuring thorough test and validation checks pass before any success claims.

What are the limitations of relying on social agreement for quality control?▼

Relying on social agreement lacks technical rigor and verification. Evidence-based code review replaces it by enforcing verification gates and subagent-driven validation to ensure actual quality and safety before merging.

Related Skills

Explore More Software Engineering Skills→
ReadyStateChangeReadyStateChange

requesting-code-review

Dispatch a code-reviewer subagent to verify changes before merge.

Official
Intermediate
mckissingermckissinger
1

land-feature

Coordinate GitHub pull request landing workflows to safely merge verified features into the main branch.

Community
Advanced
quangphu1912quangphu1912
1

requesting-code-review

Automate code review on specific commits using a subagent.

Community
Advanced
ananthapallivignesh200567ananthapallivignesh200567

receiving-code-review

Verify and implement code review feedback with technical rigor.

Community
Advanced