requesting-code-review
This skill provides a structured process for dispatching a subagent to perform code reviews on specific git commits. It mandates reviews after task completion, feature implementation, and before merging code.
Is requesting-code-review safe to install?
Review the source first: our audit of requesting-code-review's source files found 3 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill requires the execution of git commands to identify commit SHAs and involves reading local project files to provide context to the reviewer subagent.
How we audit skills: our security review methodology.
Who is this skill for?
Developers using subagent-driven development workflows who need to verify code quality and requirements adherence.
What can you do with it?
- Verifying work after completing individual tasks in subagent-driven development.
- Validating major feature implementations.
- Performing baseline checks before refactoring code.
- Obtaining a fresh perspective when stuck on a problem.
- Conducting final reviews before merging code to the main branch.
How good is this skill?
Quality score: 9/10. The skill provides clear, actionable instructions and a template-based approach for code reviews. It lacks automated integration, requiring manual execution of commands.
What does the skill file contain?
# Requesting Code Review Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work. **Core principle:** Review early, review often. ## When to Request Review **Mandatory:** - After each task in subagent-driven development - After completing major feature - Before merge to main **Optional but valuable:** - When stuck (fresh perspective) - Before refactoring (ba...
Frequently asked questions
Does the reviewer subagent see my entire session history?
No. The skill explicitly directs the agent to provide only the crafted context, excluding session history.
What information must I provide to the reviewer?
You must provide a description of the work, the plan or requirements, and the base and head git SHAs.
How should I handle feedback from the reviewer?
Fix critical issues immediately, fix important issues before proceeding, and note minor issues for later. You may push back with reasoning if the reviewer is incorrect.
Related skills
caveman-review
219.4KDevelopers and reviewers who prefer terse, actionable feedback on code changes
The caveman-review skill generates concise, one-line code review comments for pull requests. It enforces a strict format of location, problem, and fix to reduce noise in feedback.
caveman-commit
214.4KDevelopers who want to maintain clean, terse, and informative git commit histories
The caveman-commit skill generates concise commit messages following the Conventional Commits specification. It prioritizes the reasoning behind changes over the description of the changes themselves.
make-interfaces-feel-better
37.7KFrontend developers and designers using AI agents to review UI code or implement design system improvements
This skill provides design engineering principles for polishing user interfaces. It guides the agent in reviewing and implementing UI details such as typography, animations, border radii, optical alignment, and performance optimizations.
git-commit
37.6KDevelopers who want to automate the creation of semantic git commit messages based on their local code changes
The git-commit skill generates and executes standardized git commits following the Conventional Commits specification. It analyzes diffs to determine commit types, scopes, and descriptions, and manages file staging.