skills.rest
Phife726
Phife726COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Automate code-review requests with base and head SHA tracking.

Updated Mar 8, 2026
Search Tags:#git#workflow#subagent#quality-assurance#code-review#pull-request
One-click install
npx skills add https://github.com/Phife726/ds_agent --skill requesting-code-review-phife726
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Phife726/ds_agent/tree/main/requesting-code-review
Command: npx skills add https://github.com/Phife726/ds_agent --skill requesting-code-review-phife726

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After completing tasks or major feature work, teams often miss early feedback, leading to integration issues and rework. This skill provides a structured mechanism to request and review changes before merging, catching defects early.

Core Features & Use Cases

  • Enforces code-review requests after each subagent task to maintain quality and alignment.
  • Facilitates pre-merge review for major features to ensure readiness and compliance with requirements.
  • Supplies templates and guidance for reviewers to provide actionable feedback and track resolutions.

Quick Start

Request a code review after finishing a task and attach the change details for evaluation.

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 reviews before merging a pull request?▼

Automating code reviews before merging involves enforcing a documented review workflow that tracks base and head SHAs and categorizes feedback for actionable fixes.

What is the best way to request a code review after completing a subagent task?▼

The best way to request a code review after a subagent task is to trigger this automated workflow, which evaluates your changes and supplies templates for actionable reviewer feedback.

How does tracking base and head SHAs improve the code review process?▼

Tracking base and head SHAs improves the code review process by precisely identifying the commit range, ensuring that feedback is accurately categorized for fast and actionable fixes.

When do I need to enforce a pre-merge code review for major features?▼

You need to enforce a pre-merge code review for major features after completing the work to ensure readiness, maintain quality alignment, and catch integration issues early.

Can I use this workflow to catch integration issues early in my git workflow?▼

Yes, you can use this workflow to catch integration issues early in your git workflow by requesting structured reviews after subagent tasks and before merging changes to main.

How do I provide actionable feedback during a pull request review?▼

To provide actionable feedback during a pull request review, utilize the supplied templates and guidance to categorize feedback, track resolutions, and ensure quality alignment before merging.

Related Skills

Explore More Software Engineering Skills→
MeechYourGoalsMeechYourGoals
2

requesting-code-review

Dispatch a code-reviewer subagent to identify issues between Git commit SHAs.

Community
Intermediate
peancharoenpeancharoen

speckit.reviewer

Review git diffs and file paths for code issues with severity labels.

Community
Intermediate
act70255act70255

testing-qa

Automates unit, integration, E2E, and browser testing with Jest, pytest, and Playwright.

Community
Advanced
aaddrickaaddrick
5.3k

lint

Lint shell scripts with shellcheck and GitHub Actions workflows with actionlint.

Community
Basic