review-passes

Define portable review pass contracts for git-gremlin:review workflows.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/g-bastianelli/nuthouse --skill review-passes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-passes
Source: https://github.com/g-bastianelli/nuthouse/tree/main/git-gremlin/skills/review-passes
Command: npx skills add https://github.com/g-bastianelli/nuthouse --skill review-passes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for a standardized and portable code review process, reducing the complexity and effort involved in reviewing code changes.

Core Features & Use Cases

  • Shared Input Packet: Standardizes the input required for review passes, ensuring consistency.
  • Candidate Finding Schema: Facilitates the identification of potential issues in code changes.
  • Read-Only Passes: Ensures that review passes do not modify the codebase or external services.
  • Aggregation Rules: Helps in collating and validating findings from multiple review passes.

Quick Start

Execute the review-passes skill to initiate a code review process for a specific file or set of files.

Frequently Asked Questions about review-passes

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

FAQPage Schema
How do I standardize input data for automated code review passes?

Standardize input data for automated code review passes by using a shared input packet contract that ensures consistency across different review passes and workflows.

What is a portable review pass contract for code quality?

A portable review pass contract for code quality defines a standardized schema for identifying candidate findings and aggregating results across multiple review passes without modifying the codebase.

How do I aggregate findings from multiple code review passes?

Aggregate findings from multiple code review passes by applying predefined aggregation rules that collate and validate candidate findings from separate passes for correctness, conventions, tests, and risk assessment.

Can I run code review passes without modifying the codebase or external services?

Yes, you can run code review passes without modifying the codebase or external services because the review pass contract is designed to be strictly read-only.

Does the code review process support separate passes for risk assessment and test coverage?

Yes, the code review process supports separate passes for risk assessment and test coverage alongside correctness and conventions, allowing you to target specific code quality dimensions independently.

What are the limitations of using a read-only review pass contract?

The limitation of using a read-only review pass contract is that review passes cannot automatically fix identified code quality issues or modify external services, requiring manual intervention to apply changes.