skills.rest
KarlinskyS
KarlinskySCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Gather git change data and dispatch a reviewer subagent with a structured checklist.

Updated Apr 10, 2026
Search Tags:#automation#git#software-quality#code-review#self-review
One-click install
npx skills add https://github.com/KarlinskyS/hermesSkills --skill requesting-code-review-karlinskys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/KarlinskyS/hermesSkills/tree/main/software-development/requesting-code-review
Command: npx skills add https://github.com/KarlinskyS/hermesSkills --skill requesting-code-review-karlinskys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews are often delayed or skipped, leading to bugs and technical debt. This Skill enforces a consistent review process, ensuring that every feature, task, or bug fix is examined before integration.

Core Features & Use Cases

  • Self‑Review Checklist: Guides developers through a pre‑review sanity check covering conventions, tests, secrets, and debug statements.
  • Automated Context Gathering: Retrieves changed files, diff summary, and recent commits automatically.
  • Reviewer Subagent Dispatch: Sends a focused reviewer with a detailed checklist and expected output format.
  • Feedback Handling: Defines actions for critical, important, and minor issues and integrates with related development workflows.

Use cases include requesting a review after completing a major feature, after bug fixes, or when encountering a blocking problem.

Quick Start

Ask the skill to perform a code review for the latest commit in the project.

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 a code review before merging a new feature?▼

You can automate a code review by triggering a process that gathers git diff data, runs a self-review checklist, and dispatches a reviewer subagent to evaluate code quality before merging.

What steps should a self-review checklist include for a bug fix?▼

A self-review checklist should cover verifying code conventions, validating tests, scanning for hardcoded secrets, and removing debug statements before dispatching the reviewer subagent.

Does the automated code review process require access to my git repository?▼

Yes, the code review process requires repository and file system access to retrieve changed files, compile git diff summaries, and gather recent commit context for the reviewer subagent.

How does the reviewer subagent handle feedback for critical issues?▼

The reviewer subagent formats feedback into critical, important, and minor categories, defining specific required actions to resolve blocking issues before code integration.

Can I use this for refactoring tasks or is it only for new features?▼

You can use this for refactoring tasks, bug fixes, and feature implementation, applying the structured review process to any software development task requiring peer examination before merging.

Why should I run a pre-review sanity check on my code?▼

Running a pre-review sanity check catches convention violations, missing tests, and debug statements early, ensuring the reviewer subagent focuses on complex architectural issues.

Related Skills

Explore More Software Engineering Skills→
RedBoardDevRedBoardDev

pr-summary

Generates PR titles and descriptions from git branch diffs and commit history.

Community
Basic
as4584as4584
2

requesting-code-review

Dispatch a code reviewer subagent to analyze Git changes and categorize feedback.

Community
Intermediate
bobmatnycbobmatnyc
146

Requesting Code Review

Dispatch a code-reviewer subagent to review changes against plans and requirements.

Community
Basic
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced