review-work

Dispatch a code-reviewer subagent to validate changes and enforce requirements.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kagenti/humr --skill review-work-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-work
Source: https://github.com/kagenti/humr/tree/main/.agents/skills/review-work
Command: npx skills add https://github.com/kagenti/humr --skill review-work-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill accelerates quality checks by dispatching a code-reviewer subagent to verify changes before merging, keeping your work aligned with requirements.

Core Features & Use Cases

  • Dispatch a dedicated code-reviewer subagent to review changes against the plan and guidelines.
  • Preserve the user's context while the reviewer analyzes the work product.
  • Use the provided template to capture WHAT WAS IMPLEMENTED, PLAN/REQUIREMENTS, and the Git range for auditing.

Quick Start

Use the review-work skill to dispatch a code-reviewer subagent for your current change by supplying the DESCRIPTION and PLAN.

Frequently Asked Questions about review-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request code reviews?

Automate pull request code reviews by dispatching a dedicated reviewer subagent to validate changes against your plan and ensure they meet requirements before merging. It checks code quality, architecture, testing, and production readiness.

What is the best way to run pre-merge quality assurance checks?

Pre-merge quality assurance is handled by dispatching a code-reviewer subagent to verify your changes, preserving your current context while the reviewer analyzes the work product for architecture and testing alignment.

How does a subagent review changes during feature development?

A subagent reviews changes by using a structured template to capture what was implemented, the plan or requirements, and the git range for auditing, ensuring context preservation while validating the work product.

Can I check code architecture and testing readiness before a merge?

Yes, you can check code architecture and testing readiness before a merge by dispatching a reviewer subagent that validates your changes against guidelines and reports production readiness using a structured template.

Do I need to provide a plan to review code changes?

Yes, you need to supply the description and plan so the code-reviewer subagent can accurately validate the changes against your requirements and verify what was implemented within the specified git range.