requesting-code-review

Generate standardized code-review briefs for pull requests using a template.

19|2|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/CodingCossack/agent-skills-library --skill requesting-code-review-codingcossack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/CodingCossack/agent-skills-library/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/CodingCossack/agent-skills-library --skill requesting-code-review-codingcossack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often lack consistent context, scope, risk considerations, and acceptance criteria; this skill standardizes and automates the creation of review briefs to accelerate safe merges.

Core Features & Use Cases

  • Standardized templates for PR reviews
  • Guided prompts to capture WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, DESCRIPTION
  • Quick adaptation for various project sizes and teams

Quick Start

Invoke the code-reviewer subagent with the change details to generate a ready-to-merge 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 automate standardized code review briefs for pull requests?

Automate PR code review briefs by invoking a code-reviewer subagent that requires a template at templates/code-reviewer.md to capture context, scope, risks, and acceptance criteria.

What context do I need to provide for automated PR review workflows?

PR review workflows require placeholders including WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to accurately guide the automated review process.

Does the code review template work for both small fixes and multi-commit feature changes?

The code review template applies to pull requests across repositories and teams, handling both small fixes and multi-commit feature changes by standardizing the required review context.

How to capture missing scope and risk considerations in PR review processes?

Capture missing scope and risk considerations by using guided prompts within the review template to ensure all acceptance criteria and context are documented before merging code.

What is the best way to standardize PR review processes across different teams?

Standardize PR review processes across teams by implementing a consistent template that automates the creation of review briefs, ensuring safe merges regardless of project size.

Do I need a specific template file structure to generate automated PR review briefs?

You need a template file located at templates/code-reviewer.md containing specific placeholders to guide the subagent in generating standardized and ready-to-merge review briefs.