skills.rest
fred29910
fred29910COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Standardize code review requests with structured templates and SHA references.

Updated May 4, 2026
Search Tags:#templates#code-quality#code-review#software-engineering#pull-request#review-process
One-click install
npx skills add https://github.com/fred29910/migra-go --skill requesting-code-review-fred29910
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/fred29910/migra-go/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/fred29910/migra-go --skill requesting-code-review-fred29910

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and accelerates the process of requesting code reviews, ensuring reviewers receive clear context and guidance to evaluate changes effectively.

Core Features & Use Cases

  • Template-driven reviews: Provides a consistent code-review template (code-reviewer.md) to capture WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION.
  • Context-rich guidance: Includes a dedicated structure to help reviewers understand the change scope, risks, and acceptance criteria.
  • Governance and traceability: Enforces review before merging to improve code quality and accountability.

Quick Start

Fill in the code-reviewer template with your change details and trigger the review by supplying the BASE_SHA and HEAD_SHA to package the diff.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I standardize a pull request for a formal code review?▼

Standardize a pull request by applying a structured code-review template that captures WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to provide consistent reviewer guidance and traceability.

What context does a reviewer need to evaluate a feature branch diff?▼

A reviewer needs the change scope, risks, acceptance criteria, BASE_SHA, and HEAD_SHA to evaluate a feature branch diff, which the code-review template organizes to ensure clear context and effective evaluation.

How do I package a diff for a merge request review?▼

Package a diff for a merge request review by supplying the BASE_SHA and HEAD_SHA into the code-review template to define the change boundaries and trigger the formal review process.

Can I use a template for both bug fixes and feature branch code reviews?▼

Yes, you can use the same template for both bug fixes and feature branch code reviews, as it applies to software development workflows requiring formal review processes for various merge requests.

What is the best way to enforce governance and traceability before merging code?▼

Enforce governance and traceability before merging by standardizing code-review requests with a template that documents the implementation details and requirements, ensuring accountability and quality control.

Related Skills

Explore More Software Engineering Skills→
futuregeraldfuturegerald
6

requesting-code-review

Automate structured code-review requests with required template fields.

Community
Intermediate
catu-aicatu-ai
12

harness-land

Merge an approved pull request after confirming an archived harness plan.

Official
Intermediate
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
cwijayasundaracwijayasundara
3

harness-core

Automate build, test, deployment, and code review in CI/CD pipelines.

Community
Advanced