comprehensive-review

Reviews code changes against seven criteria and posts a mandatory review artifact to GitHub issues.

Updated Jan 1, 2026

Search Tags:#code review #pull request #github #issue tracking #security review #quality gate #self-review

Ready to run

npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill comprehensive-review-sarkarshivaditya-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: comprehensive-review
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/comprehensive-review
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill comprehensive-review-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code that ships without structured self-review carries blindspots, security risks, and style drift into pull requests. This Skill enforces a repeatable 7-criteria review process and blocks PR creation until a documented review artifact is posted to the GitHub issue. ## Core Features & Use Cases - 7-Criteria Review: Systematically checks blindspots, clarity, maintainability, security, performance, documentation, and style with concrete checklists per criterion. - Mandatory GitHub Artifact: Posts a structured review summary as an issue comment using an exact markdown format; a PreToolUse hook and review-gate block PR creation without it. - Findings Workflow: Every finding must be fixed or deferred with a linked tracking issue, keeping "Unaddressed" at zero. - Use Case: After implementing a feature touching authentication middleware, run this review to catch an SQL injection risk, invoke the security-review skill, fix the findings, and post the completion artifact before opening the PR. ## Quick Start Perform a comprehensive code review of my latest changes and post the review artifact to the 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 run a comprehensive code review before creating a pull request?▼

Run git diff to list changed files, then evaluate the code against the 7 criteria: blindspots, clarity, maintainability, security, performance, documentation, and style. Document all findings, fix or defer each one with a tracking issue, and post the review artifact to the GitHub issue.

What are the 7 code review criteria in this workflow?▼

The criteria are blindspots, clarity/consistency, maintainability, security risks, performance implications, documentation, and standards/style. Each criterion includes a checklist of concrete questions such as edge-case handling, N+1 queries, and input validation.

Why is my pull request blocked after code review?▼

PR creation is blocked by a PreToolUse hook and review-gate until a review artifact is posted to the GitHub issue in the exact required format. The artifact must show "Unaddressed: 0" and "Review Status: COMPLETE".

When is a security review mandatory during code review?▼

A security review is mandatory whenever changed files match security-sensitive patterns such as auth, middleware, api, password, token, or secret. In that case the security-review skill or security-reviewer subagent must be invoked and the artifact marked "Security-Sensitive: YES".

Can I defer code review findings instead of fixing them?▼

Yes, but only by creating a tracking issue for each deferred finding and linking it in the review artifact. Deferring without a tracking issue is not permitted, and the unaddressed count must remain zero.