skills.rest
Moonsong-Labs
Moonsong-LabsOFFICIAL
Explore all skills by this author →
GitHub

requesting-code-review

Dispatch the code-reviewer subagent to review code and categorize findings by severity.

3|2|Updated Mar 9, 2026
Search Tags:#subagent#quality-assurance#code-review#pull-request#engineering-workflow#review-process
One-click install
npx skills add https://github.com/Moonsong-Labs/knowledge-work-plugins --skill requesting-code-review-moonsong-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Moonsong-Labs/knowledge-work-plugins/tree/main/core-engineering/skills/requesting-code-review
Command: npx skills add https://github.com/Moonsong-Labs/knowledge-work-plugins --skill requesting-code-review-moonsong-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch core-engineering:code-reviewer to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.

Core Features & Use Cases

  • Mandatory review after each task in subagent-driven development to prevent escalation.
  • Standardized feedback templates and severity classification for quick triage.
  • Useful before merges to main and during major feature delivery.

Quick Start

Dispatch the core-engineering:code-reviewer subagent with the task details to begin the review.

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 to main?▼

Automate code review before merging by dispatching a code-reviewer subagent with task details. This enforces a structured review template and categorizes findings by severity to catch issues early.

What is the best way to review code in a subagent-driven engineering workflow?▼

Reviewing code in a subagent-driven engineering workflow is best handled by dispatching a code-reviewer subagent. It evaluates precisely crafted context rather than session history, keeping the reviewer focused on the work product.

How do code review subagents categorize pull request feedback?▼

Code review subagents categorize pull request feedback using standardized templates and severity classification. This structured approach allows developers to quickly triage issues found during feature work or refactors.

Can I use an automated code reviewer for bug fixes and refactors?▼

Yes, you can use an automated code reviewer for bug fixes and refactors. Dispatching a code-reviewer subagent after each development task prevents issues from cascading across all types of engineering work.

Why does a code review subagent use isolated context instead of session history?▼

A code review subagent uses isolated context instead of session history to keep the evaluation focused strictly on the work product. This prevents thought process bias and preserves your session context for continued development.

When do I need to dispatch a code reviewer during feature delivery?▼

You need to dispatch a code reviewer during major feature delivery and before merges to main. Applying mandatory review after each subagent development task ensures issues are caught before they escalate.

Related Skills

Explore More Software Engineering Skills→
randoneeringrandoneering

requesting-code-review

Dispatch a reviewer subagent to gather context for structured code-review requests.

Community
Intermediate
duanegoodnerduanegoodner

land

Merges a GitHub pull request via squash and removes the feature branch.

Community
Intermediate
lifangdalifangda
43

requesting-code-review

Dispatch a code-reviewer subagent to assess code changes against requirements.

Community
Advanced
romiluz13romiluz13
161

review-workflow

Coordinate specialized subagents to review code for security, performance, and UX findings.

Community
Intermediate