review-checklist

Automate a 30-item PR review checklist for quality gates before merging.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/LeeHusung/harness --skill review-checklist-leehusung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-checklist
Source: https://github.com/LeeHusung/harness/tree/main/.claude/skills/review-checklist
Command: npx skills add https://github.com/LeeHusung/harness --skill review-checklist-leehusung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR open reviews can miss critical quality gates, leading to regressions and miscommunication. This Skill automates a 30-item final review checklist to standardize checks before merging and to provide clear, auditable guidance for developers and reviewers.

Core Features & Use Cases

  • Automated validation of correctness, scope, security, observability, and documentation criteria for each PR.
  • Clear remediation guidance with highlighted missing items and actionables to accelerate safe merges.
  • Use Case: Before merging a feature branch, run the checklist to ensure all required checks are satisfied and logs are available for auditing.

Quick Start

Run the final PR review checklist against the current pull request before opening.

Frequently Asked Questions about review-checklist

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

FAQPage Schema
How do I automate a pull request review checklist before merging?

Automating a pull request review checklist verifies correctness, scope, security, observability, and documentation criteria before merging. This Skill runs a 30-item check to standardize quality gates and provide auditable remediation guidance.

What is a PR quality gate and how does it work?

A PR quality gate is a formal validation step ensuring code changes meet specific standards before merging. It works by applying an automated checklist to verify ADR compliance, steering conformance, and audit-ready change logs.

How do I ensure code review security and observability criteria are met?

To ensure code review security and observability criteria are met, run an automated final review checklist that validates these specific domains. It highlights missing items and provides clear remediation guidance for safe merges.

Can I use an automated checklist for any pull request workflow?

Yes, you can use this automated checklist for any pull request workflow requiring formal quality gates. It applies strict input validation and structured output to ensure non-destructive operation across diverse merge processes.

What is the best way to provide audit-ready change logs for a pull request?

The best way to provide audit-ready change logs is to run an automated 30-item PR review checklist before opening the merge. This process standardizes checks and generates clear, auditable guidance for developers and reviewers.

Why does my PR open review miss critical quality gates?

PR open reviews miss critical quality gates due to manual oversight. Automating a 30-item final review checklist solves this by standardizing checks across correctness, scope, security, observability, and documentation before merging.