comprehensive-review

Review code against seven criteria and post findings to GitHub issues.

10|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/troykelly/codex-skills --skill comprehensive-review-troykelly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comprehensive-review
Source: https://github.com/troykelly/codex-skills/tree/main/skills/comprehensive-review
Command: npx skills add https://github.com/troykelly/codex-skills --skill comprehensive-review-troykelly

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures code quality and adherence to standards by enforcing a rigorous, multi-point code review process before any Pull Request can be created, preventing the introduction of bugs, security vulnerabilities, and maintainability issues.

Core Features & Use Cases

  • Mandatory 7-Criteria Review: Enforces a comprehensive check across blindspots, clarity, maintainability, security, performance, documentation, and style.
  • Artifact Posting: Requires a detailed review artifact to be posted to the GitHub issue, serving as auditable proof of review.
  • PR Gate Enforcement: Integrates with hooks to block PR creation until the review artifact is complete and all findings are addressed or deferred.
  • Use Case: After implementing a new feature, a developer uses this skill to perform a thorough self-review, documenting findings and ensuring all issues are resolved before submitting the code for team review, thereby increasing the likelihood of a smooth merge.

Quick Start

Perform a comprehensive code review on the latest changes and post the artifact to the associated GitHub issue.

Frequently Asked Questions about comprehensive-review

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

FAQPage Schema
How do I enforce a mandatory code review before a pull request is created?

To enforce a mandatory code review before a pull request, integrate hooks to block PR creation until a detailed review artifact is posted to the GitHub issue and all findings are resolved.

What criteria are checked during a comprehensive GitHub pull request review?

A comprehensive GitHub pull request review checks seven criteria: blindspots, clarity, maintainability, security, performance, documentation, and style to prevent bugs and ensure project standards.

How do I document a self-review for a new feature before submitting code?

To document a self-review for a new feature, generate a detailed review artifact covering seven criteria and post it to the associated GitHub issue, serving as auditable proof of code quality.

Does this code review process work with GitHub issues to track findings?

Yes, this code review process works directly with GitHub issues by requiring the generation and posting of a detailed review artifact to the relevant issue to track and audit findings.

What happens to a pull request if code review findings are not addressed?

If code review findings are not addressed or properly deferred, the pull request creation remains blocked by integrated hooks until all identified security, maintainability, and quality issues are resolved.

Why should I use a multi-criteria code review gate for software development?

You should use a multi-criteria code review gate to catch critical issues, security vulnerabilities, and maintainability problems early in the development cycle before code is merged.