skills.rest
MohamedAbdallah-14
MohamedAbdallah-14COMMUNITY
Explore all skills by this author →
GitHub

wz:requesting-code-review

Request formal code reviews with routing guidance and standardized templates.

3|1|Updated Mar 16, 2026
Search Tags:#collaboration#code-quality#quality-assurance#code-review#pull-request#dev-workflow#review-process
One-click install
npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-requesting-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wz:requesting-code-review
Source: https://github.com/MohamedAbdallah-14/Wazir/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-requesting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated, formal code reviews reduce merge risks by ensuring changes are examined before integration, improving quality and consistency across the codebase.

Core Features & Use Cases

  • Routing guidance for who should review and when to trigger a review.
  • A canonical checklist and templates to standardize feedback and approvals.
  • Use cases include per-task reviews, feature milestones, and before-merge gates in CI pipelines.

Quick Start

Run wz:requesting-code-review to start a formal review workflow for the latest changes.

Frequently Asked Questions about wz:requesting-code-review

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

FAQPage Schema
How do I request a code review for a pull request?▼

To request a code review, you can trigger a formal review workflow that applies routing guidance to determine who should examine the changes before integration. This ensures your pull request meets merge requirements.

When do I need to initiate a formal code review process?▼

You need a formal code review process after completing a development task or before opening a merge request. Triggering reviews at these milestones ensures changes are examined for quality and consistency before integration.

How does a code review workflow coordinate reviewers?▼

A code review workflow coordinates reviewers using a canonical routing strategy and a recommended subagent workflow. This approach standardizes feedback by providing human-readable templates to guide approvals.

What is the best way to standardize feedback for code reviews?▼

The best way to standardize code review feedback is using a canonical checklist and human-readable templates. This ensures consistent approvals and reduces merge risks across your development workflow.

Can I integrate code review checkpoints into my CI pipeline?▼

Yes, you can integrate formal code reviews as before-merge gates in CI pipelines. This applies routing guidance to trigger reviews automatically, ensuring changes meet requirements before integration.

Why should I kick off code reviews early in the dev workflow?▼

You should kick off code reviews early to reduce merge risks by ensuring changes are examined before integration. Early reviews improve quality and consistency across the codebase throughout the development workflow.

Related Skills

Explore More Software Engineering Skills→
tstaplertstapler
8

code-review

Enforces evidence-based code reviews before merges and completion claims.

Community
Advanced
Clay-HHKClay-HHK
2

code-review-excellence

Apply structured code-review workflows to pull requests with checklists and templates.

Community
Advanced
s3nex-coms3nex-com

pr-merge-orchestrator

Coordinate pull request lifecycle from review through merge with mandatory gates.

Community
Advanced
Marwan78888Marwan78888
16

requesting-code-review

Route code changes to a code-review subagent for structured evaluation.

Community
Intermediate