skills.rest
kaminocorp
kaminocorpOFFICIAL
Explore all skills by this author →
Website𝕏@kaminocorpoGitHub

requesting-code-review

Dispatches reviewer subagents to validate code changes against requirements before merging.

1|Updated Mar 12, 2026
Search Tags:#workflow#testing#quality assurance#code review#security review#subagent#merge validation
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill requesting-code-review-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill requesting-code-review-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written under time pressure often ships with blind spots — missed edge cases, security gaps, and logic errors the author cannot see. This Skill enforces a systematic review process that catches critical issues before they reach the main branch. ## Core Features & Use Cases - Structured Review Dispatch: Uses delegate_task to send a focused reviewer subagent with a full checklist covering correctness, quality, testing, security, and performance. - Tiered Feedback Triage: Classifies findings as Critical, Important, or Minor so you know exactly what blocks a merge and what can wait. - Quality Gates: Defines mandatory pass criteria (no critical issues, all tests green, APPROVE verdict) before merging. - Use Case: After finishing a feature branch with changes to auth and user models, dispatch a reviewer subagent with the diff context, receive a verdict of REQUEST_CHANGES with two critical security findings, fix them, and re-review before merging. ## Quick Start Ask the agent to review the changes on your current branch using the requesting-code-review process before merging to main.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a code review before merging a branch?▼

Run a self-review checklist first, gather context with git diff and git log, then dispatch a reviewer subagent via delegate_task with the changed files and a review checklist. Act on the tiered feedback before merging.

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing major features, after bug fixes, and always before merging to main. Reviews are also valuable when stuck or before refactoring.

What should a code review checklist include?▼

Cover correctness against requirements, edge case handling, error handling, code readability, meaningful test coverage, security vulnerabilities like injection or exposed secrets, and performance issues such as N+1 queries.

What issues should block a merge in code review?▼

Critical issues block merges: security vulnerabilities, broken functionality, data loss risk, and test failures. Important issues like missing edge cases or unclear code should be fixed before merge when possible.

What if I disagree with reviewer feedback?▼

Push back with technical reasoning and evidence. Show code or tests that prove the implementation works, and request clarification rather than arguing without support.

Related Skills

Explore More Software Engineering Skills→
forktruckaforktrucka

engineer

Implement and fix Homebridge SoundTouch plugin TypeScript code with tests.

Community
Advanced
RachasumanthRachasumanth

prepare-pr

Rebases GitHub PRs onto main branch and commits reviewed fixes with automated checks.

Community
Advanced
phraphra

code-review

Review modified code files and auto-fix mechanical issues.

Community
Advanced
moduloMomentsmoduloMoments
7

pair

Facilitate pair programming sessions for code review and collaborative file changes.

Official
Intermediate