code-reviewer

Generate structured AI review documents from GitHub repository audits.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hoonzinope/skills --skill code-reviewer-hoonzinope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/hoonzinope/skills/tree/main/code-reviewer
Command: npx skills add https://github.com/hoonzinope/skills --skill code-reviewer-hoonzinope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Reviewers spend time writing up findings after reading through codebases. This Skill automates that work by generating a structured AI Review document into .documents/review/AI_REVIEW.md without modifying source code.

Core Features & Use Cases

  • Automated Review Generation: Converts repository observations into a formal AI Review document.
  • Template-driven Output: Uses a scaffold template and a checklist to ensure consistency.
  • Non-destructive Workflow: Writes only to the designated .documents/review/AI_REVIEW.md.

Quick Start

Run the scaffold_doc.py script to create a dated .documents/review/AI_REVIEW.md using assets/TEMPLATE.md and references/CHECKLIST.md.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code review findings for a GitHub repository?

Automate code review findings by running a scaffold script that evaluates your repository against a checklist and writes actionable results into a structured AI_REVIEW.md document without modifying source code.

Does automated code review modify my source code during maintenance audits?

Automated code review does not modify source code. It operates non-destructively by writing all observations and findings exclusively into a designated review document within your repository.

What's the best way to generate a structured review document for a codebase refactor?

Generate a structured review document for refactoring by applying a standardized template and validation checklist, ensuring consistent formatting and comprehensive coverage of repository observations.

Can I use a checklist to validate AI review output for consistency?

Yes, you can validate AI review output using a dedicated checklist reference file, which ensures the generated review document meets structural requirements and covers necessary audit criteria.

What limitations exist when writing repository observations into review documents?

The primary limitation is output location: all repository observations must be written specifically into the .documents/review/AI_REVIEW.md file, restricting where the automated review findings are stored.