review

Reviews build output against specifications, code quality standards, and compliance gates before shipping.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill review-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/jokerman89/lintel/tree/main/skills/review
Command: npx skills add https://github.com/jokerman89/lintel --skill review-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unreviewed code often reaches release with spec deviations, quality defects, or compliance gaps that surface too late. This Skill enforces a structured adversarial review between build and ship so defects are caught and prioritized before delivery. ## Core Features & Use Cases - Three-stage review pipeline: Runs spec compliance first, then code quality (correctness, security, performance, style, test coverage), then pack-defined compliance gates, with each stage gating the next. - Priority-based findings: Classifies issues as P1 (blocks ship), P2 (must fix), or P3 (nit), with fix loops capped at three iterations and operator decision points. - Audit-ready artifacts: Produces review-report.md and compliance-report.md with per-stage verdicts, cross-artifact consistency checks, and an optional independent Codex outside-voice review. - Use Case: After finishing a feature build, run the review to verify every planned task matches the implementation exactly, catch a P1 security flaw, and generate a ship-ready verdict with documented evidence. ## Quick Start Ask the agent to review the current build output against the plan and produce a ship-readiness verdict with prioritized findings.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code against a specification before shipping?▼

Run the review after the build phase completes. It checks each planned task against the actual diff for exact spec compliance first, then evaluates code quality, and finally fires any compliance gates, producing a ship-ready verdict.

How do I review a pull request or diff standalone?▼

Invoke the review with a diff range such as origin/main..HEAD or a specific PR number. The same three-stage pipeline runs against that scope without requiring a full build cycle.

What happens when a P1 finding is detected during review?▼

A P1 finding blocks shipping until resolved. The operator chooses to fix immediately via a build loop-back, defer with an ADR, or explicitly accept the risk, with a maximum of three fix iterations.

When should I skip the review phase?▼

Skip it for research-only or docs-only intents where no code was built. It should also not run before the build completes, since mid-task checks belong to the build phase's own review cycle.

Does the review support security and dependency audits?▼

Yes, it can dispatch specialized agents including security auditors and a dependency auditor for CVE, license, and supply-chain checks. Compliance-related gates fire only when the active pack defines them.