skills.rest
Axeloooo
AxelooooCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Requests a code review for a specific git change set using BASE_SHA and HEAD_SHA.

Updated Oct 16, 2025
Search Tags:#quality assurance#code review#production readiness#git shas#subagent workflow#triage feedback
One-click install
npx skills add https://github.com/Axeloooo/TheDataBay --skill requesting-code-review-axeloooo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Axeloooo/TheDataBay/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/Axeloooo/TheDataBay --skill requesting-code-review-axeloooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents regressions and production incidents by ensuring changes receive a focused, requirements-aligned code review before they merge.

Core Features & Use Cases

  • Mandatory review checkpoints: Triggers reviews after each subagent task, after major features, and before merging to main.
  • Context-safe reviewer instructions: Packages only what the reviewer needs (what changed, what it should do, and the git SHAs) to keep feedback relevant.
  • Actionable feedback handling: Guides how to triage Critical/Important/Minor issues and when to push back with technical evidence.

Quick Start

Use requesting-code-review after completing your latest subagent task and provide the base and head SHAs plus a one-paragraph description of what you implemented.

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 for a specific git change set?▼

You request a code review for a git change set by preparing the BASE_SHA and HEAD_SHA from your repository, providing a description of the implementation, and dispatching a code-reviewer subagent to analyze the targeted changes.

When should I trigger a targeted code review in a subagent workflow?▼

In a subagent workflow, you should trigger a targeted code review after completing each subagent task, finishing major feature work, and immediately before merging code to the main branch.

What is the purpose of providing BASE_SHA and HEAD_SHA for production readiness checks?▼

Providing BASE_SHA and HEAD_SHA for production readiness checks isolates the exact code changes, ensuring the reviewer subagent only evaluates what changed to keep feedback relevant and context-safe.

How do I triage severity-ranked feedback from a code reviewer?▼

You triage severity-ranked feedback from a code reviewer by categorizing issues into Critical, Important, and Minor levels, resolving blockers first, and pushing back with technical evidence when necessary.

Can I use this code review approach before merging to main?▼

Yes, you can use this code review approach before merging to main, as it serves as a mandatory checkpoint to prevent regressions and production incidents by validating changes against requirements.

Related Skills

Explore More Software Engineering Skills→
alffeialffei
69

requesting-code-review

Dispatch a code-reviewer subagent to validate git changes before merging.

Community
Intermediate
minfengyuanminfengyuan
1

requesting-code-review

Evaluate git code changes and classify issues by severity.

Community
Intermediate
LiGoldragonLiGoldragon
1

requesting-code-review

Create and dispatch code review requests with revision ranges.

Community
Intermediate
conejoRojoconejoRojo

requesting-code-review

Dispatch a subagent to evaluate git-based changes against project requirements.

Community
Advanced