review-standard

Automate code review guidance to enforce documentation quality and code reuse.

1|2|Updated Sep 17, 2025

Search Tags:#automation #documentation #quality #lint #code-review #pull-requests

Ready to run

npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill review-standard-madrid1011

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-standard
Source: https://github.com/MAdrid1011/Zircon-VLIW/tree/main/.claude/skills/review-standard
Command: npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill review-standard-madrid1011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable code review framework to ensure documentation quality, adherence to project standards, and opportunities for code reuse during review.

Core Features & Use Cases

Enforces documentation completeness, interface clarity, and reuse opportunities during reviews invoked via /code-review.
Produces actionable, traceable findings aligned with the document-guideline standards.
Use Case: Before merging, run milestone reviews to ensure changes align with guidelines and avoid duplication.

Quick Start

Trigger the /code-review command on a pull request to generate a structured, actionable report.

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 in pull requests?▼

Automate code review for documentation completeness by triggering a standardized review command on pull requests to evaluate interface clarity, type safety, and reuse opportunities, producing a structured, actionable report aligned with project guidelines.

What is the best way to enforce code reuse standards during a milestone review?▼

The best way to enforce code reuse standards during a milestone review is to apply a systematic code review framework that evaluates changes against explicit project standards, identifying duplication and generating traceable findings before merging.

How does standardized code review guidance check interface clarity and type safety?▼

Standardized code review guidance checks interface clarity and type safety by evaluating README and interface documentation completeness, enforcing traceability with explicit standard references, and analyzing change impact to produce structured findings.

Can I use automated code review to ensure traceability with project guidelines before merging?▼

Yes, you can use automated code review to ensure traceability before merging by running milestone reviews that check changes against document-guideline standards, verifying documentation completeness and interface clarity to generate actionable reports.

What should a structured code review report include for documentation quality evaluation?▼

A structured code review report for documentation quality evaluation should include actionable, traceable findings aligned with project guidelines, covering interface documentation completeness, type safety checks, change impact analysis, and identified code reuse opportunities.