ZES-requesting-code-review

Name: ZES-requesting-code-review
Availability: InStock
Author: zescode

Dispatch a code reviewer subagent to audit code changes for ZES compliance.

Updated Jul 8, 2026

Search Tags:#automation #quality assurance #code review #security #subagent #zes

Ready to run

npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-requesting-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ZES-requesting-code-review
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/ZES-requesting-code-review
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-requesting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents bugs and security vulnerabilities from reaching production by automating the code review process through a dedicated subagent, ensuring consistent quality without manual oversight.

Core Features & Use Cases

Automated Review Dispatch: Triggers a specialized subagent to evaluate code changes against ZES-specific security and quality standards.
Context-Aware Auditing: Provides the reviewer with precise commit ranges and requirements, keeping the evaluation focused and efficient.
Use Case: Before merging a new feature into the main branch, use this skill to verify that your code adheres to ZES port-binding security rules and error-handling patterns.

Quick Start

Request a code review by providing the base commit hash, the head commit hash, and a brief description of your changes to the subagent.

Frequently Asked Questions about ZES-requesting-code-review

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

FAQPage Schema

How do I automate code review and security audits before a merge?▼

Automated code review dispatches a specialized subagent to evaluate code changes against quality and security standards, ensuring consistent verification of system architecture and maintainability before merging without manual oversight.

What is a subagent code review process for software development workflows?▼

A subagent code review process automatically triggers a specialized reviewer to audit precise commit ranges, keeping the evaluation focused on security patterns, error handling, and infrastructure compliance for software development workflows.

How do I check my code for ZES-specific infrastructure compliance like port binding and secret management?▼

Checking ZES infrastructure compliance involves running a context-aware audit on your code changes to verify adherence to specific rules for port binding security, error-handling patterns, and secret management.

What do I need to provide to trigger an automated code reviewer subagent?▼

To trigger the automated code reviewer subagent, you need to provide the base commit hash, the head commit hash, and a brief description of your changes to supply precise context for the evaluation.

Does automated code review work without manual oversight for pre-merge checks?▼

Automated code review works without manual oversight by dispatching a dedicated subagent to perform focused security audits and quality checks, preventing bugs and vulnerabilities from reaching production environments.

When do I need to run a security audit on my code changes?▼

You need to run a security audit on your code changes before merging a new feature into the main branch to verify that your code adheres to required security patterns and maintainability standards.