skills.rest
beyondwen
beyondwenCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Submit code changes for formal review using a standardized code-reviewer.md template.

Updated Mar 30, 2026
Search Tags:#automation#git#workflow#template#review#quality-assurance#code-review
One-click install
npx skills add https://github.com/beyondwen/track-record-new --skill requesting-code-review-beyondwen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/beyondwen/track-record-new/tree/main/.gemini/skills/requesting-code-review
Command: npx skills add https://github.com/beyondwen/track-record-new --skill requesting-code-review-beyondwen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines code quality assurance by routing changes to a dedicated reviewer proxy and providing a standardized feedback template to ensure requirements are met before merging.

Core Features & Use Cases

  • Structured Review Request: Standardizes how changes are submitted for review using a predefined template and placeholder fields.
  • Template-Driven Feedback: Guides reviewers with a consistent evaluation format including what was implemented, plan, and base/head references.
  • Diff-Aware Context: Encourages including git SHAs and diffs to give reviewers precise context.
  • Workflow Integration: Fits into typical development workflows by triggering a code-review step after task completion.
  • Usage Guidance: Provides clear instructions on when to request review and how to act on feedback.

Quick Start

After finishing a task, dispatch the code-reviewer proxy and complete the code-reviewer.md template to submit your change for review.

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 code review before merging to main?▼

To request a code review, dispatch the code-reviewer proxy and complete the code-reviewer.md template with your BASE_SHA and HEAD_SHA references to collect structured feedback.

When should I submit code changes for a formal review?▼

Submit code changes for formal review when you finish tasks, implement significant features, perform refactors, apply major fixes, or need guidance on blockers before merging to main.

What is a template-driven code review workflow?▼

A template-driven code review workflow standardizes feedback by using a predefined code-reviewer.md format to categorize issues, ensuring requirements are met before merging code.

Do I need git SHAs to submit changes for code review?▼

Yes, you must provide BASE_SHA and HEAD_SHA references when submitting changes. These git SHAs give the reviewer precise diff-aware context for evaluating the code.

What's the best way to standardize code quality assurance feedback?▼

The best way to standardize code quality assurance is using a structured template that categorizes issues, detailing what was implemented, the plan, and base/head git references.

Can I use this code review template for minor bug fixes?▼

This code review template targets significant features, refactors, and major fixes. Minor bug fixes that do not require formal quality assurance can bypass this structured review process.

Related Skills

Explore More Software Engineering Skills→
FelixBitSoulFelixBitSoul
2

requesting-code-review

Dispatch a code-reviewer agent after task completion for structured Git workflow feedback.

Community
Advanced
zhuyingcoderzhuyingcoder

requesting-code-review

Orchestrates pre-merge code reviews by delegating a code-reviewer proxy.

Community
Intermediate
seankao31seankao31

subagent-driven-development

Dispatch isolated subagents to implement plan tasks with per-task reviews.

Community
Advanced
TheBushidoCollectiveTheBushidoCollective
187

sop-rfc2119

Enforce RFC 2119 keyword usage in standard operating procedures.

Official
Advanced