code-review

Review pull requests against project plans and HOTL contracts.

25|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/yimwoo/hotl-plugin --skill code-review-yimwoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/yimwoo/hotl-plugin/tree/main/skills/code-review
Command: npx skills add https://github.com/yimwoo/hotl-plugin --skill code-review-yimwoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews can miss plan alignment and HOTL governance gates, leading to risky merges and inconsistent quality.

Core Features & Use Cases

  • Enforces plan alignment, test coverage, and HOTL governance before merge.
  • Provides a repeatable, auditable review checklist for software PRs.
  • Helps ensure secure and compliant merges by documenting severity decisions and gate approvals.

Quick Start

Run a targeted code-review pass against the latest pull request to verify alignment with the HOTL contracts.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce governance gates and plan alignment before merging a pull request?

To enforce governance gates before merging, run a code review that verifies pull requests against project plans and HOTL contracts, ensuring test coverage and plan alignment are met prior to approval.

What is the best way to document severity decisions during a pull request review?

Documenting severity decisions during a pull request review requires explicit handling of issues and recorded gate approvals, creating an auditable checklist that proves secure and compliant merges.

How does a pre-merge code review verify HOTL workflow steps?

A pre-merge code review verifies HOTL workflow steps by checking the pull request against HOTL contracts, validating that all required governance gates and code quality checks are explicitly satisfied.

Can I automate quality checks for software engineering pull requests?

You can automate quality checks for software engineering pull requests by applying a repeatable review checklist that validates test coverage and HOTL governance gates before the merge.

Why does my manual code review miss plan alignment and governance gates?

Manual code reviews miss plan alignment and governance gates because they lack a structured verification process, leading to inconsistent quality and risky merges without documented severity decisions.