requesting-code-review

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

7|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/cloudfieldcz/cf-powers --skill requesting-code-review-cloudfieldcz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/cloudfieldcz/cf-powers/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/cloudfieldcz/cf-powers --skill requesting-code-review-cloudfieldcz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates early issue detection by dispatching cf-powers:code-reviewer to review code changes before they cascade.

Core Features & Use Cases

  • Dispatch cf-powers:code-reviewer subagent to catch issues before they cascade.
  • Defines a standardized review workflow: after each task, after completing major features, and before merge to main.
  • Provides structured feedback through the code-reviewer template and recommended actions.

Quick Start

Trigger a code review by dispatching the cf-powers:code-reviewer subagent after you complete a task.

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 in a subagent workflow?

Automate code reviews by dispatching a dedicated review subagent to evaluate code changes after each task. This enforces a standardized review process and returns structured feedback to catch issues early before they cascade.

When should I trigger an automated code review during feature development?

Trigger an automated code review after completing each task in subagent-driven development, after finishing major features, or before merging to main. This early issue detection prevents defects from compounding across the development lifecycle.

What is a code-reviewer template and how does it structure feedback?

A code-reviewer template enforces a standard code-review process by defining parameters like BASE_SHA and HEAD_SHA. It returns structured feedback with recommended actions, ensuring consistent quality assurance across all code changes.

Can I integrate automated code reviews into my merge process without external dependencies?

Yes, the code review process operates with no external dependencies. It dispatches a review subagent using a standardized template to evaluate changes before merge to main, returning structured feedback directly within your workflow.

What's the best way to catch code issues before merging to main?

The best way is dispatching a code-reviewer subagent with BASE_SHA and HEAD_SHA parameters before merging to main. This enforces a standard code-review process, returns structured feedback, and catches issues early before they cascade.

Why use a subagent for code reviews instead of manual review processes?

A subagent for code reviews automates early issue detection by enforcing a standardized review process with structured templates. This catches issues before they cascade, providing consistent quality assurance without manual intervention.