skills.rest
esneiderbravo
esneiderbravoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Generate standardized code-review briefings with evaluation checklists for reviewers.

1|Updated Apr 17, 2026
Search Tags:#workflow#template#subagent#quality-assurance#code-review#pull-request
One-click install
npx skills add https://github.com/esneiderbravo/hackaton --skill requesting-code-review-esneiderbravo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/esneiderbravo/hackaton/tree/main/.github/skills/requesting-code-review
Command: npx skills add https://github.com/esneiderbravo/hackaton --skill requesting-code-review-esneiderbravo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating code reviews can be inconsistent and delayed. This guide provides a standardized workflow to request and evaluate code changes, ensuring timely, thorough feedback.

Core Features & Use Cases

  • Structured briefing: generates WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION blocks for reviewers to assess.
  • Workflow integration: invoked after each subagent task, after completing major features, or before merging to main.
  • Guided evaluation: outlines criteria for code quality, architecture, testing, and production readiness to focus feedback and reduce back-and-forth.

Quick Start

Invoke the request-review workflow after completing a task to generate a reviewer-ready briefing for the reviewer.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
What is a structured code review briefing and why do I need one?▼

A structured code review briefing is a standardized prompt containing implementation details, plan requirements, and commit SHAs. It ensures reviewers receive consistent context to evaluate code quality, architecture, testing, and production readiness, reducing delayed or inconsistent feedback.

How do I generate a code review request for a pull request?▼

Invoke the request-review workflow after completing a task or before merging to main. This generates a reviewer-ready briefing by populating standardized placeholders like WHAT_WAS_IMPLEMENTED, BASE_SHA, HEAD_SHA, and DESCRIPTION blocks for evaluation.

When should I request a code review in my workflow?▼

You should request a code review after each subagent task completes, after finishing major features, or before merging to main. This timing enforces timely feedback and ensures structural changes are evaluated against production readiness checklists.

What evaluation criteria should a code review checklist include?▼

A code review checklist should include criteria for code quality, architecture, testing, and production readiness. This guided evaluation focuses reviewer feedback on specific structural and functional requirements to minimize back-and-forth communication.

Related Skills

Explore More Software Engineering Skills→
aberrantCodeaberrantCode
1

requesting-code-review

Reviews a range of commits for defects and requirement compliance.

Community
Intermediate
franroafranroa

requesting-code-review

Dispatch a code-reviewer subagent with Git SHAs for production-readiness assessment.

Community
Intermediate
JNZader-VaultJNZader-Vault

wave-workflow

Orchestrates parallel task waves with ViteKanban integration, automating branches and pull requests.

Official
Intermediate
mattstrublemattstruble
2

code-reviewer

Orchestrate a parallel four-reviewer code review workflow on PR diffs.

Community
Advanced