review-standard

Name: review-standard
Availability: InStock
Author: Ayazhan

Review code changes for documentation, quality, reuse, and type safety.

Updated Feb 9, 2026

Search Tags:#software engineering #quality assurance #code review #documentation #refactoring #standards

Ready to run

npx skills add https://github.com/ayazhankadessova/essential-skills --skill review-standard-ayazhankadessova

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-standard
Source: https://github.com/ayazhankadessova/essential-skills/tree/main/plugins/essential-skills/skills/review-standard
Command: npx skills add https://github.com/ayazhankadessova/essential-skills --skill review-standard-ayazhankadessova

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, repeatable process to ensure code changes meet high standards for documentation, code quality, reuse, and advanced architectural considerations before merging.

Core Features & Use Cases

Three-Phase Review: Systematically assesses documentation completeness, code quality/reuse, and advanced aspects like type safety.
Standards-Driven: Enforces consistent, project-specific rules for all code reviews.
Actionable Feedback: Generates clear recommendations for improvements.
Use Case: Before merging a new feature, run this Skill to guarantee all new code is well-documented, leverages existing utilities, adheres to project conventions, and avoids common pitfalls like unnecessary indirection.

Quick Start

Run a comprehensive code review on the latest changes, focusing on documentation, quality, and advanced checks.

Frequently Asked Questions about review-standard

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

FAQPage Schema

How do I automate code review for documentation completeness and architectural standards?▼

To perform a code review for merge readiness, run a systematic three-phase process that evaluates documentation completeness, code quality, reuse of existing utilities, and advanced architectural concerns, resulting in a structured report detailing findings.

What does a standards-driven code review process check for before merging?▼

A standards-driven code review checks for documentation completeness, code quality, reuse of existing utilities, module focus, interface documentation, type safety, and architectural concerns to ensure changes meet project conventions before merge.

How can I check if my new code reuses existing utilities and avoids unnecessary indirection?▼

You can check code reuse and indirection by running a multi-phase review that systematically assesses whether new code leverages existing utilities and validates advanced architectural concerns against defined standards, providing feedback on merge readiness.

When do I need to run a multi-phase code review on my software changes?▼

You need a multi-phase code review before merging new features to guarantee all new code is well-documented, adheres to project conventions, leverages existing utilities, and avoids common pitfalls like unnecessary indirection or type safety issues.

Can I enforce project-specific conventions and type safety checks during a code review?▼

Yes, you can enforce project-specific conventions and type safety by validating code changes against defined standards during the advanced architectural phase of the review, ensuring interface documentation and module focus meet required criteria.

What is the best way to generate actionable feedback for code refactoring before a merge?▼

The best way to generate actionable refactoring feedback is to execute a comprehensive review that assesses code quality and architectural concerns, producing a structured report that details findings and recommendations for merge readiness.