TRIP-review

Reviews code changes against a project checklist and generates structured review reports.

614|89|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/PiLastDigit/TRIP-workflow --skill trip-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: TRIP-review
Source: https://github.com/PiLastDigit/TRIP-workflow/tree/main/skills/TRIP-review
Command: npx skills add https://github.com/PiLastDigit/TRIP-workflow --skill trip-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often lack consistent criteria and produce unstructured feedback that is hard to audit later. This Skill provides a manual fallback and audit path for reviewing code against a single-source-of-truth checklist, producing standardized review records.

Core Features & Use Cases

  • Checklist-Driven Review: Applies a shared checklist covering functional requirements, code quality, architecture, error handling, security, and performance, with severity classification from Critical to Suggestions.
  • Structured Review Records: Renders a standardized markdown template into docs/3-code-review/CR_wa_vx.y.z.md with findings, checklist outcomes, and an approval verdict.
  • Approval Gate: Enforces completion criteria such as no remaining critical or major issues, successful builds, and passing tests before approval.
  • Use Case: After shipping version 1.2.0 without an automated review loop, run this Skill to audit the release against the project checklist and commit a formal review record to the docs folder.

Quick Start

Ask the AI to review version 1.2.0 using the TRIP-review checklist and save the review report to the docs folder.

Frequently Asked Questions about TRIP-review

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

FAQPage Schema
How do I run a manual code review with a checklist?

Invoke the review skill with a version or feature argument, then walk each checklist section against the change. Failing items become findings classified by severity, and results are saved as a structured markdown file in docs/3-code-review/.

What should a code review checklist include?

A solid checklist covers functional requirements, code quality, architectural compliance, error handling, security, and performance. This Skill's checklist also defines severity levels from Critical to Suggestions and an approval gate requiring no open critical or major issues.

When should I use manual review instead of automated review?

Use this manual path to audit past versions, review unplanned work, or replace the automated Codex review loop when it is unavailable. Normal reviews happen automatically inside the TRIP-2-implement phase.

How are code review findings classified by severity?

Findings are classified as Critical (block deployment, e.g., security vulnerabilities), Major (require immediate fix, e.g., incorrect logic), Minor (should fix, e.g., style issues), or Suggestions (nice to have, e.g., optimizations).

Where are code review reports stored?

Review records are saved to docs/3-code-review/ using the naming pattern CR_wa_vx.y.z.md, where a is the project week and x.y.z is the version. The report follows a standard template with findings, checklist outcomes, and a verdict.