skills.rest
bluefishs
bluefishsCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Generate structured code-review requests with YAML frontmatter and severity-based issue documentation.

Updated Dec 30, 2025
Search Tags:#automation#subagent#quality-assurance#code-review#pull-request#merge-prep#review-process
One-click install
npx skills add https://github.com/bluefishs/CK_Missive --skill requesting-code-review-bluefishs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/bluefishs/CK_Missive/tree/main/.claude/skills/_shared/shared/superpowers/requesting-code-review
Command: npx skills add https://github.com/bluefishs/CK_Missive --skill requesting-code-review-bluefishs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use structured code-review requests to catch issues early and prevent defects from cascading into production.

Core Features & Use Cases

  • Dispatch a code-reviewer subagent after each task or before merging to main, ensuring alignment with requirements.
  • Provide a standardized template for reviewers with clear WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, and BASE/HEAD SHAs.
  • Maintain traceability and proactive feedback loops in subagent-driven development.

Quick Start

Ask the subagent to initiate a code-review request after task completion.

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 code review requests before a pull request merge?▼

You can automate code review requests by dispatching a code-reviewer subagent before merging to main. This initiates structured reviews that catch issues early and ensure alignment with requirements.

What is a structured code review template for subagent-driven development?▼

A structured code review template provides standardized fields including WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, and BASE/HEAD SHAs. This maintains traceability and proactive feedback loops in subagent-driven workflows.

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

You should initiate a code review request after each task completion, after finishing major features, or before merging to main. This prevents defects from cascading into production environments.

How do I document base and head diffs for pull request quality assurance?▼

Document base and head diffs by enforcing a YAML frontmatter with name and description, then using a code-reviewer template to generate reviews that record issues by severity for quality assurance.

Can I use a subagent to enforce code review standards before merging?▼

Yes, you can dispatch a subagent to enforce code review standards before merging. It uses a standardized template to verify requirements alignment and categorize discovered issues by severity.

Related Skills

Explore More Software Engineering Skills→
WesleyMFrederickWesleyMFrederick

requesting-code-review

Dispatch a code-reviewer subagent to review Git changes between BASE_SHA and HEAD_SHA.

Community
Basic
a-tabijia-tabiji

merge

Merge reviewed pull requests into main with squash merge and branch cleanup.

Community
Intermediate
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic