skills.rest
hugo-berendi
hugo-berendiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Dispatch a code-review subagent with base and head SHAs.

3|Updated May 31, 2024
Search Tags:#automation#workflow#quality assurance#code review#task management#pull requests
One-click install
npx skills add https://github.com/hugo-berendi/yomi --skill requesting-code-review-hugo-berendi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/hugo-berendi/yomi/tree/main/.opencode/skills/requesting-code-review
Command: npx skills add https://github.com/hugo-berendi/yomi --skill requesting-code-review-hugo-berendi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of obtaining timely, structured code reviews by routing tasks to a dedicated reviewer subagent, helping catch issues early in development.

Core Features & Use Cases

  • Directed reviews: Automatically route completed work to a code-review subagent for feedback.
  • Early defect detection: Ensures issues are caught after each task, after major features, and before merging to main.
  • Structured feedback: Uses a clear template to capture implemented changes, planned scope, base and head SHAs, and a concise description for reviewers.

Quick Start

Dispatch the code-reviewer subagent for the latest task by providing the implemented changes, plan or requirements, and the base and head SHAs, then review feedback and iterate.

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 after completing a development task?▼

Automating code reviews after a task involves dispatching a code-review subagent with a structured template containing base and head SHAs, implemented changes, and requirements. This routes completed work directly to a dedicated reviewer for early defect detection.

What information do I need to include in a structured code review template?▼

A structured code review template requires base and head SHAs, a description of what was implemented, the plan or requirements, and a concise description to guide feedback. Capturing these details ensures the reviewer has full context to catch issues.

When should I request a code review during subagent-driven development?▼

Code reviews should be requested after each task in subagent-driven development, after completing major features, and before merging to main. This timing catches issues early and prevents defects from cascading further into the development cycle.

What is the best way to catch defects before merging to main?▼

The best way to catch defects before merging to main is dispatching a dedicated reviewer subagent using a structured template with base and head SHAs. This ensures timely, structured feedback that identifies issues before they cascade.

Can I route pull requests to a subagent for quality assurance feedback?▼

Yes, routing pull requests to a code-review subagent provides quality assurance feedback by applying a structured review template. The subagent evaluates the implemented changes against the plan and requirements using the provided base and head SHAs.

Related Skills

Explore More Software Engineering Skills→
lifangdalifangda
43

requesting-code-review

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

Community
Advanced
cloudfieldczcloudfieldcz
7

requesting-code-review

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

Official
Intermediate
AtaraxiaEpiphanyAtaraxiaEpiphany

parallel-step

Orchestrate parallel task execution for software development tracks via wave-based dispatch.

Community
Advanced
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced