review

Parse diffs and apply a two-pass checklist to classify code review findings.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/indigoai-us/hq --skill review-indigoai-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/indigoai-us/hq/tree/main/template/.claude/skills/review
Command: npx skills add https://github.com/indigoai-us/hq --skill review-indigoai-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers perform rigorous pre-landing code reviews by automatically parsing diffs, applying a two-pass analysis, and surfacing issues with precise file:line references to ensure quality and safety before PRs.

Core Features & Use Cases

  • Two-pass analysis: CRITICAL issues block PR creation; INFORMATIONAL findings appear in the PR body.
  • Repo-local and shared checklists: loads the appropriate review checklist to guide findings.
  • Precise reporting: cites file:line for every finding to enable fast fixes.
  • Use cases include reviewing new changes before PRs, evaluating post-implementation diffs, and gated reviews for critical security or correctness concerns.

Quick Start

Run the pre-landing review on your current diff to surface blocking issues and recommendations.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pre-landing code reviews for pull requests?

Automate pre-landing code reviews by parsing git diffs and applying a two-pass checklist to classify findings. It surfaces CRITICAL issues that block PR creation and INFORMATIONAL findings for the PR body.

What is a two-pass checklist analysis for git diffs?

A two-pass checklist analysis for git diffs evaluates code changes sequentially to classify findings. The first pass identifies CRITICAL blocking issues, and the second surfaces INFORMATIONAL recommendations within the PR body.

Can I use custom review checklists for my repository's pull requests?

Yes, you can load repo-local and shared checklists to guide code review findings. This ensures the automated pre-landing review applies your specific quality-assurance rules to the diff.

How do I get precise file and line references from an automated code review?

Get precise file and line references by running the pre-landing review on your diff. It cites exact file:line locations for every finding, enabling developers to quickly locate and fix issues before PR creation.

When do I need a pre-landing code review for security and correctness?

You need a pre-landing code review when evaluating post-implementation diffs or gating critical security and correctness concerns. It applies deterministic feedback to ensure code quality and safety before PRs.