skills.rest
idoberk
idoberkCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Request structured code review feedback using a git range and implementation summary.

Updated Jan 26, 2026
Search Tags:#testing#code review#pull request#production readiness#merge readiness#git diff
One-click install
npx skills add https://github.com/idoberk/BoQAppFront --skill requesting-code-review-idoberk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/idoberk/BoQAppFront/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/idoberk/BoQAppFront --skill requesting-code-review-idoberk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you request structured code review at the right time so defects, missing requirements, and readiness issues are caught before changes are merged.

Core Features & Use Cases

  • Review Triggers: Use it after each task, after major features, before merging, or when you need a fresh perspective on a difficult bug.
  • Focused Context: It prepares a precise review package with the implementation summary, the expected requirements, and the git range so the reviewer stays focused on the work product.
  • Actionable Feedback: It organizes findings into strengths, critical issues, important issues, minor issues, recommendations, and a clear merge-readiness verdict.

Quick Start

Ask for a code review by briefly describing what you built, what it should satisfy, and which commits should be compared.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a structured code review before a pull request merge?▼

To request a structured code review, provide a concise implementation summary, the expected requirements, and the git range of your recent changes so the reviewer can evaluate correctness, testing, architecture, and production readiness.

What should I include in a merge readiness review for recent code changes?▼

A merge readiness review requires an implementation summary, the expected requirements, and a git diff range. The feedback organizes findings into strengths, critical issues, important issues, minor issues, recommendations, and a clear merge verdict.

When should I trigger a code review for a bug fix or major refactor?▼

Trigger a code review after completing a task, finishing a major feature, finalizing a refactor, fixing a difficult bug, or when preparing a merge candidate to catch defects and missing requirements before changes reach main.

How does a focused git diff review evaluate production readiness?▼

A focused git diff review evaluates production readiness by comparing the implementation summary against expected requirements, categorizing feedback into critical issues, minor issues, and a final merge-readiness verdict.

Can I get actionable code review feedback on specific git commit ranges?▼

Yes, you can request actionable feedback on specific git commit ranges by providing the implementation summary, expected requirements, and the exact git range to keep the reviewer focused on the work product.

Related Skills

Explore More Software Engineering Skills→
RedBoardDevRedBoardDev

pr-summary

Generates PR titles and descriptions from git branch diffs and commit history.

Community
Basic
mshaheerzmshaheerz
1

review-merge-readiness

Review git diffs against project plans and requirements for merge readiness.

Community
Intermediate
eng-vmessiaheng-vmessiah
2

ai-regression-testing

Automate regression tests validating API response shapes and state integrity.

Community
Intermediate
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic