skills.rest
AvaTar-ArTs
AvaTar-ArTsCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Automate pre-merge code-review tasks by dispatching a review subagent.

Updated May 11, 2026
Search Tags:#git#workflow#development#subagent#quality-assurance#code-review
One-click install
npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill requesting-code-review-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/AvaTar-ArTs/my-supremepowers/tree/main/qwen_skills/superpowers-requesting-code-review
Command: npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill requesting-code-review-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams enforce structured code reviews by automating the delegation and tracking of review tasks within a development workflow, reducing merge risks and improving code quality.

Core Features & Use Cases

  • Dispatch subagent reviews: Route code changes to a dedicated review subagent for analysis and feedback before merging.
  • Capture required metadata: Gather what was implemented, plan/requirements, and key diffs for reviewers.
  • Integrated feedback loop: Translate reviewer feedback into actionable tasks and status updates.

Quick Start

Trigger a code-review session for the latest task by dispatching the code-reviewer subagent with the required task details.

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 pre-merge code review tasks in my git workflow?▼

Automating pre-merge code review tasks is handled by routing feature development changes to a dedicated code-review subagent. This subagent collects implementation details, requirements, and diffs to present actionable reviewer feedback before merging.

What is the best way to trigger code reviews after a major refactor?▼

Triggering code reviews after a major refactor involves dispatching a code-review subagent with the required task details. The subagent captures what was implemented, the plan, and key diffs to generate actionable feedback for reviewers.

Does this code review workflow require any specific dependencies or components?▼

This code review workflow does not require specific dependencies or components to function. It operates independently by delegating tasks to a subagent and routing implementation details to collect reviewer feedback.

Can I use a subagent to collect implementation details for quality assurance?▼

Using a subagent to collect implementation details for quality assurance is the core mechanism of this workflow. It gathers what was implemented, plan requirements, and key diffs to route to reviewers and provide actionable feedback.

How does automated code review routing catch issues early in development?▼

Automated code review routing catches issues early by dispatching changes to a review subagent during feature development or post-implementation pushes. This translates reviewer feedback into actionable tasks and status updates before merge risks escalate.

Related Skills

Explore More Software Engineering Skills→
xuithoixuithoi

requesting-code-review

Dispatch a subagent to review code changes against requirements and architectural standards.

Community
Intermediate
kage1020kage1020

check-pr-comments

Apply pull request comment feedback as code changes and verify tests.

Community
Intermediate
jayhjenkinsjayhjenkins

requesting-code-review

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

Community
Basic
ZJUxjyZJUxjy

requesting-code-review

Dispatch a subagent to analyze code changes against requirements and quality standards.

Community
Intermediate