requesting-code-review

Request code reviews for pending changes by gathering git SHAs and dispatching a code-reviewer subagent.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/PlazaCC/antes-da-tela --skill requesting-code-review-plazacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/PlazaCC/antes-da-tela/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/PlazaCC/antes-da-tela --skill requesting-code-review-plazacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often merge code without thorough review, leading to bugs and regressions. This skill ensures systematic code review by automating the request process.

Core Features & Use Cases

  • Automated SHA extraction: Retrieves base and head commit identifiers for precise diffing.
  • Template-driven subagent dispatch: Populates a review template and triggers the code-reviewer subagent.
  • Feedback integration: Provides structured guidance on handling critical, important, and minor issues.
  • Applicable scenarios: After completing a task, before merging a feature branch, or when stuck and needing fresh perspective.

Quick Start

Ask the code-reviewer subagent to evaluate the changes between the current HEAD and the previous commit before proceeding with the merge.

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 feature branch?

Automating code review involves retrieving base and head commit SHAs, populating a review template, and dispatching a subagent to evaluate pending changes. This ensures quality and compliance before merging a feature branch.

What is the process for requesting a code review on pending git changes?

Requesting code review uses automated SHA extraction to identify precise diffs, then dispatches a subagent with a populated template to evaluate changes. It provides structured feedback on critical, important, and minor issues.

Can I get structured feedback on critical and minor issues during a pre-merge code review?

Yes, this code review process provides structured guidance categorizing feedback into critical, important, and minor issues. It dispatches a subagent to evaluate pending changes and returns prioritized actionable feedback.

Does automated code review work without additional dependencies or environment setup?

Yes, automated code review operates with no external dependencies. It directly extracts git SHAs and dispatches the code-reviewer subagent to evaluate pending changes within your existing development environment.

When do I need to trigger an automated code review during development?

You need automated code review after completing a task, before merging a feature branch, or when stuck and needing a fresh perspective. It ensures code quality and compliance by evaluating pending changes.