skill-staged-review

Review code for spec compliance and quality in two passes.

28|3|Updated May 10, 2026
One-click install
npx skills add https://github.com/CES-Ltd/Lumi --skill skill-staged-review-ces-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-staged-review
Source: https://github.com/CES-Ltd/Lumi/tree/main/resources/seed/octopus/skills/skill-staged-review
Command: npx skills add https://github.com/CES-Ltd/Lumi --skill skill-staged-review-ces-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of conducting thorough and systematic code reviews by structuring the process into two distinct passes: spec compliance verification and code quality assessment.

Core Features & Use Cases

  • Two-Stage Review Process: Guides users through loading intent contracts, validating success criteria and boundaries, and then performing detailed quality checks including stub detection and external model-based assessments.
  • Automated Checks: Scans code for TODOs, empty functions, suspicious returns, and mock data, providing quick insights into code completeness.
  • Use Case: When preparing a major feature or PR, developers can run this Skill to ensure adherence to specifications and maintain high-quality code standards before merging.

Quick Start

Invoke the skill on your current codebase and review the structured output for compliance and quality status.

Frequently Asked Questions about skill-staged-review

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

FAQPage Schema
What is a two-pass code review process for spec compliance and quality?

A two-pass code review initially validates code against predefined intent contracts and success boundaries, then executes a secondary pass to evaluate overall code quality metrics and structural completeness.

How do I automate code scanning for TODOs, empty functions, and mock data?

You can automate code scanning by invoking the skill on your codebase to quickly detect TODOs, empty functions, suspicious returns, and mock data, providing immediate insights into code completeness.

When do I need to verify specification compliance before merging a major feature?

You need specification compliance verification when preparing a major feature or PR, ensuring the code strictly adheres to predefined contracts and maintains high quality standards before merging.

Can I use external evaluation models for quality checks during code review?

Yes, external model-based assessments are integrated into the quality evaluation pass, allowing development teams to perform detailed external evaluations alongside automated checks for complex projects.

Does structured code review separate specification validation from quality metrics?

Structured code review explicitly separates specification validation from quality metrics by guiding users through loading intent contracts first, followed by targeted quality checks like stub detection.

What are the limitations of automated code scanning for complex project specifications?

Automated code scanning focuses primarily on detecting incomplete implementations like TODOs and mock data, meaning complex specification boundary violations may still require external evaluation to fully validate.