code-review

Review Night-Orch code changes against an 8-point checklist for conventions and security.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/shllg/night-orch --skill code-review-shllg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/shllg/night-orch/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/shllg/night-orch --skill code-review-shllg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Night-Orch code reviews can be streamlined and standardized using this checklist, ensuring consistent quality and adherence to project conventions.

Core Features & Use Cases

  • Structured Review: Follows an 8-point checklist to systematically review code changes.
  • Immutability and Boundary Enforcement: Ensures changes don't mutate critical state or violate adapter boundaries.
  • Environment Isolation: Ensures that worker environments are isolated and secure.
  • Phase Checkpointing: Tracks progress with phase-start and phase-complete logs.
  • Metrics and Error Handling: Emphasizes robust metrics logging and error handling.
  • Label Idempotency: Ensures label mutations are idempotent.
  • TypeScript Strictness: Enforces TypeScript best practices.

Quick Start

Run the checklist against your Night-Orch code changes using 'night-orch code-review'.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce a checklist for Night-Orch code reviews?

You can enforce a Night-Orch code review checklist by running 'night-orch code-review' to evaluate changes against an 8-point structured list. This ensures your codebase consistently adheres to project conventions and security best practices.

What does a structured Night-Orch code review cover?

A structured Night-Orch code review covers immutability, adapter boundary enforcement, environment isolation, phase checkpointing, metrics logging, error handling, label idempotency, and TypeScript strictness. It systematically verifies that code changes maintain project integrity.

Can I check TypeScript strictness and boundary enforcement in Night-Orch?

Yes, you can check TypeScript strictness and boundary enforcement in Night-Orch using the code review checklist. It specifically verifies that changes do not mutate critical state and enforces strict TypeScript best practices.

Do I need an isolated worker environment for Night-Orch code changes?

Yes, you need an isolated worker environment for Night-Orch code changes. The review checklist explicitly includes environment isolation checks to ensure that worker environments remain secure and separate during development.

Why are label mutations and phase checkpointing important in Night-Orch?

Label mutations and phase checkpointing are important in Night-Orch to ensure idempotency and track progress. The review checklist verifies that label changes are idempotent and validates phase-start and phase-complete logs.