requesting-code-review

Dispatch a code-reviewer subagent to enforce merge gates with machine-readable YAML blocks.

Updated Sep 25, 2024
One-click install
npx skills add https://github.com/kwam1na/athena --skill requesting-code-review-kwam1na
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/kwam1na/athena/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/kwam1na/athena --skill requesting-code-review-kwam1na

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatches a code-review workflow to ensure quality before merging, keeping the reviewer focused on the work product and preventing cascading issues.

Core Features & Use Cases

  • Automated gating with a code-reviewer subagent to surface issues after each task or feature.
  • Pre-merge quality checks for major features and before merging to main.
  • Enforces a machine-readable merge gate contract to standardize reviews and approvals.

Quick Start

Instruct the system to dispatch the code-reviewer after completing a task to obtain a standardized, machine-readable review block before merging.

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 pull request?

Automate code review before merging by dispatching a code-reviewer subagent after each major feature is complete. This enforces a pre-merge quality gate, surfacing issues early to prevent cascading problems during task completion.

What is a merge gate and how does it standardize pull request approvals?

A merge gate standardizes pull request approvals by enforcing a machine-readable YAML block with decision counts. This contract structures reviewer feedback, ensuring consistent quality checks before code merges to main.

How do I set up automated quality assurance checks for subagent-driven development?

Set up automated quality assurance for subagent-driven development by dispatching a code-reviewer subagent after each task. It applies a structured template to catch issues immediately, enforcing a merge gate before integrating to main.

Can I enforce a machine-readable review contract for git pull requests?

Yes, you can enforce a machine-readable review contract for git pull requests by requiring a YAML block with decision counts. The code-reviewer subagent uses this format to structure feedback and standardize the merge gate approval process.

When should I dispatch a code-reviewer subagent during feature development?

Dispatch a code-reviewer subagent after completing each task in subagent-driven development, after finishing major features, and before merging to main. This gating strategy catches issues early and prevents them from cascading.