skills.rest
lapaixkemsdortshlee-svg
lapaixkemsdortshlee-svgCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Review completed code changes against stated requirements with severity-ranked findings.

Updated Apr 3, 2026
Search Tags:#testing#code review#pull request#software quality#subagent#merge check
One-click install
npx skills add https://github.com/lapaixkemsdortshlee-svg/AyitiMarket --skill requesting-code-review-lapaixkemsdortshlee-svg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/lapaixkemsdortshlee-svg/AyitiMarket/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/lapaixkemsdortshlee-svg/AyitiMarket --skill requesting-code-review-lapaixkemsdortshlee-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify completed work before it spreads problems into later tasks, making it easier to catch bugs, requirement gaps, and design issues early.

Core Features & Use Cases

  • Pre-merge validation: Review implemented changes against requirements before merging to main.
  • Major feature checks: Confirm that a newly built feature matches the plan and is production-ready.
  • Subagent workflow support: Use a dedicated reviewer context so feedback stays focused on the code, not the implementation history.

Quick Start

Ask the assistant to review the completed code changes against the original requirements before you merge them.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I review code changes against requirements before a pull request merge?▼

Pre-merge code review validates completed diffs against original requirements to catch bugs and design issues early. It analyzes architecture and testing readiness, providing severity-ranked findings and a clear merge verdict before integration.

What is the best way to check if a feature implementation is production-ready?▼

Production readiness checks evaluate feature implementations against the original plan. Code review focuses on the diff, architecture, and testing to confirm the feature matches requirements and is safe for deployment.

Can I use a subagent workflow to keep code review feedback focused?▼

Subagent workflow support isolates the review context so feedback stays focused on the code itself. This prevents implementation history from cluttering the review and keeps findings centered on the actual diff.

How does a pre-merge check identify defects in refactoring checkpoints?▼

Pre-merge checks review code changes at refactoring checkpoints to identify defects before they cascade. The review examines the diff, architecture, and testing, returning severity-ranked findings and a merge verdict.

When do I need a dedicated code review for bug fixes?▼

A dedicated code review is needed for bug fixes when you want to verify the changes against requirements and catch related defects. It assesses the diff and testing to ensure the fix is production-ready before merge.

Related Skills

Explore More Software Engineering Skills→
andreciniandrecini
2

code-review

Review .NET/C# pull requests or staged diffs and classify issues by severity.

Community
Intermediate
tony30552001tony30552001

land-and-deploy

Coordinate PR merge, CI wait, production deployment, and canary health checks.

Community
Advanced
vladm3105vladm3105
16

code-review

Automate code review across multi-language repositories with static analysis and security scanning.

Community
Advanced
kevinnftkevinnft
13

ci-cd-and-automation

Automate CI/CD quality gates for lint, type checks, tests, and security audits.

Community
Advanced