skills.rest
park-kyungchan
park-kyungchanCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Aug 27, 2026
Search Tags:#automation#git#quality assurance#code review#development workflow#subagent#pre-merge
One-click install
npx skills add https://github.com/park-kyungchan/palantir --skill requesting-code-review-park-kyungchan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/park-kyungchan/palantir/tree/main/.claude/plugins/cache/claude-plugins-official/superpowers/4.2.0/skills/requesting-code-review
Command: npx skills add https://github.com/park-kyungchan/palantir --skill requesting-code-review-park-kyungchan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams require an early, formal code-review step in subagent-driven development to prevent defects from propagating before merge.

Core Features & Use Cases

  • Dispatch a code-reviewer subagent to assess changes before merging.
  • Generate structured feedback including strengths, issues, and readiness for production.
  • Integrate with task workflows by citing WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION.

Quick Start

After finishing a task, prepare the review input using WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION, then run the code-reviewer subagent with a git range and interpretation of feedback.

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 before merging a branch?▼

Automating pre-merge code review requires dispatching a code-reviewer subagent to assess changes using a defined git range and structured change summary. It generates formal feedback on strengths, issues, and production readiness before integration into main branches.

When do I need to trigger a subagent for code review in a development workflow?▼

Subagent code review is needed after each task completion or major feature delivery in subagent-driven development workflows. It serves as an early, formal review step to prevent defects from propagating before merging into main branches.

What inputs are required to run an automated code review subagent?▼

Running an automated code review subagent requires a defined change summary containing WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. These inputs provide the context and git range needed to generate structured feedback.

Does subagent-driven code review work without external dependencies?▼

Subagent-driven code review works without external dependencies, operating entirely within the development workflow. It relies on internal subagent dispatching and structured change summaries rather than external tools or APIs to generate feedback.

What is the best way to structure feedback for pre-merge code review?▼

The best way to structure pre-merge code review feedback is to generate a formal assessment covering strengths, issues, and production readiness. This structured feedback is produced by the code-reviewer subagent based on the provided change summary and git range.

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
Suara17Suara17

requesting-code-review

Automate code-review requests using a code-reviewer subagent and git SHAs.

Community
Basic
cowwoccowwoc
101

cat:merge-subagent

Merge a completed subagent branch into the parent task branch with cleanup.

Community
Advanced
cloudfieldczcloudfieldcz
7

requesting-code-review

Dispatch the cf-powers:code-reviewer subagent to review code changes and return structured feedback.

Official
Intermediate