review

Persist audit sets and structured completion states for Nexus lifecycle reviews.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill review-lapagayo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/canonical/review
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill review-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical Nexus review enables governance-grade verification by persisting the required current audit set and a structured review completion state for the lifecycle. It ensures the right artifacts and verdicts are attached before moving to subsequent stages.

Core Features & Use Cases

  • Persist the required current audit set and a structured review state for the Nexus lifecycle.
  • Support canonical prompts like review the change, audit this build, dual-review before ship, and lifecycle gating across build, qa, and ship on multiple hosts.
  • Integrate with the Nexus routing and gating model, guaranteeing the explicit gate verdicts and artifact contracts used by /ship and /qa transitions.

Quick Start

Run the governed review workflow on a changed build to initialize the audit set and gate state for governance.

Frequently Asked Questions about review

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

FAQPage Schema
How do I persist an audit set and gate state for Nexus lifecycle review?

Canonical Nexus review records the required current audit set and a structured review state for the lifecycle. It ensures the right artifacts and explicit gate verdicts are attached before moving to subsequent stages like qa or ship.

How do I run a dual-review before ship across multiple hosts?

You can run a dual-review before ship across multiple hosts by triggering the governed review workflow through the /nexus do dispatcher. It coordinates lifecycle gating and records explicit gate verdicts required for the ship transition.

Can I use this review workflow to gate transitions between build, qa, and ship?

Yes, this review workflow supports lifecycle gating between build, qa, and ship stages. It integrates with the Nexus routing and gating model to guarantee explicit gate verdicts and artifact contracts are used by these transitions.

Do I need the /nexus do dispatcher to execute a governed build audit?

Yes, executing a governed build audit requires integration with the nexus skill manifests and the /nexus do dispatcher. The dispatcher handles the front-end routing guidance and artifact collection necessary for the review process.

What artifacts and verdicts are required before moving to the ship stage?

Before moving to the ship stage, the required current audit set and explicit gate verdicts must be persisted. The review workflow ensures these artifact contracts are attached as part of the Nexus lifecycle completion state.