comprehensive-code-review

Conducts structured code reviews using a collaborative checklist covering per-file analysis and risks.

3|Updated Feb 15, 2025
One-click install
npx skills add https://github.com/mark-torres10/ai_tools --skill comprehensive-code-review-mark-torres10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comprehensive-code-review
Source: https://github.com/mark-torres10/ai_tools/tree/main/skills/comprehensive-code-review
Command: npx skills add https://github.com/mark-torres10/ai_tools --skill comprehensive-code-review-mark-torres10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ad-hoc code reviews often miss cross-cutting concerns, testing gaps, and risk assessment. This Skill enforces a structured, checklist-driven review process so every review covers per-file analysis, cross-cutting concerns, testing, and risks consistently. ## Core Features & Use Cases - Checklist-Driven Reviews: Loads the COMPREHENSIVE_CODE_REVIEW_CHECKLIST.md from the ai_tools tree and applies every section to the review. - Automatic Path Discovery: Resolves the ai_tools root by checking for a workspace submodule first, then falling back to a canonical local path. - Structured Findings: Organizes review output by checklist sections, including per-file notes, cross-cutting concerns, and risk assessment. - Use Case: A developer finishing a feature branch asks for a thorough review before merging; the Skill walks through each checklist section and produces evidence-based findings scoped to the stated goal. ## Quick Start Ask the AI to perform a comprehensive code review of my current changes using the collaborative review checklist.

Frequently Asked Questions about comprehensive-code-review

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

FAQPage Schema
How do I run a comprehensive code review with this Skill?

Ask for a comprehensive, thorough, or collaborative code review of your current work. The Skill locates the COMPREHENSIVE_CODE_REVIEW_CHECKLIST.md file, gathers required context, and produces findings organized by each checklist section.

What does the collaborative code review checklist cover?

The checklist covers per-file analysis, cross-cutting concerns, testing, risks, and context. The Skill addresses every section or explicitly states why a section does not apply to the current review.

What happens if the review checklist file is not found?

The Skill first checks for an ai_tools submodule in the workspace root, then falls back to a canonical local path. If the checklist is still missing, it asks the user for the checklist path and stops.

Can I use this review process without providing full context?

Partial context is acceptable. The Skill infers or gathers required inputs and uses the checklist items to solicit missing information such as key files, per-file notes, and cross-cutting concerns.

When should I not use a comprehensive checklist review?

Avoid it for quick sanity checks or trivial changes where a full per-file and risk assessment is unnecessary overhead. It is designed for thorough reviews of meaningful work scoped to a stated goal.