skills.rest
dfmonaco
dfmonacoCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Request a focused code review with diff range and requirements.

Updated Mar 17, 2017
Search Tags:#git#code review#verification#diff#subagent#scope
One-click install
npx skills add https://github.com/dfmonaco/dotfiles --skill requesting-code-review-dfmonaco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/dfmonaco/dotfiles/tree/main/archive/agents-skills/requesting-code-review
Command: npx skills add https://github.com/dfmonaco/dotfiles --skill requesting-code-review-dfmonaco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures critical code changes receive a thorough, focused review before they are merged, reducing the risk of bugs, scope drift, and unverified assumptions.

Core Features & Use Cases

  • Define Review Scope: Gather a concise summary of what changed, the associated requirements, the git diff range, and any verification already performed.
  • Launch Review Subagent: Invoke the task tool with an oracle or general subagent to conduct an analysis‑only review.
  • Triage Feedback: Prioritize critical and important issues, capture minor notes, and determine the next steps in the development workflow.
  • Workflow Integration: Seamlessly hand off to receiving-code-review, verification-before-completion, or branch‑finishing skills as needed. Use cases include after completing a major feature, before creating a pull request, or whenever an independent assessment is required.

Quick Start

Ask the requesting-code-review skill to review the current diff against the plan.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I get a focused code review before merging a git diff?▼

To get a focused code review before merging, you provide the git diff range, requirement description, and verification context to launch an analysis-only review subagent.

When should I request a code review for a feature or bug fix?▼

You should request a code review when a substantial feature, refactor, or bug fix reaches a stable checkpoint and needs validation against its original requirements.

What do I need to define the scope of a code review?▼

Defining the scope of a code review requires a concise summary of changes, the associated requirements, the git diff range, and any verification already performed.

Can I launch a subagent to conduct an analysis-only code review?▼

Yes, you can invoke the task tool with an oracle or general subagent to conduct an analysis-only review of your change set without making modifications.

How do I triage feedback after a code review?▼

Triage code review feedback by prioritizing critical and important issues, capturing minor notes, and determining the next steps in the development workflow.

What is the best way to integrate code review into my development workflow?▼

Integrate code review by handing off to receiving-code-review, verification-before-completion, or branch-finishing skills to ensure changes are validated before merging.

Related Skills

Explore More Software Engineering Skills→
remix-runremix-run
33.3k

review-pr

Review Remix pull requests from a local checkout for correctness and security.

Official
Intermediate
greglambgreglamb
1

executing-plans

Execute written implementation plans with structured review, task tracking, and verification.

Community
Intermediate
miles990miles990

finishing-a-development-branch

Present four merge, PR, keep, or discard options after tests pass.

Community
Intermediate
LucaDeLeoLucaDeLeo
1

gsd:second-opinion

Run OpenAI Codex to provide a read-only second opinion on code or architecture.

Community
Intermediate