review-closeout

Record review readiness and close user validation after verification passes.

Updated Mar 7, 2026

Search Tags:#workflow #python #verification #evidence #review #task #closeout

Ready to run

npx skills add https://github.com/alexization/git-ranker-workflow --skill review-closeout

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-closeout
Source: https://github.com/alexization/git-ranker-workflow/tree/main/.codex/skills/review-closeout
Command: npx skills add https://github.com/alexization/git-ranker-workflow --skill review-closeout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifications pass and reviews risk remaining open without formal closure; this Skill ensures recording of review readiness and closing of user validation once verification succeeds.

Core Features & Use Cases

Validate that every phase is completed before closing the task.
Record review readiness using the provided Python workflow script.
Close user validation with notes to produce final state and evidence.
Provide auditable artifacts such as updated task.json indicating state=completed and associated evidence.

Quick Start

Run the workflow to record review readiness and close user validation for a task after the verification passes.

Frequently Asked Questions about review-closeout

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

FAQPage Schema

How do I automate task closeout after verification passes in a Python workflow?▼

Task closeout after verification is automated by running a Python workflow script that records review readiness and closes user validation, ensuring all phases reach completed status before final closure.

What is review readiness closure and when do I need to record it?▼

Review readiness closure is the formal process of documenting that a task has passed verification and is ready for final validation. You need it when verifications succeed but reviews risk remaining open without formal closure.

How do I ensure state consistency across all verification phases before closing a task?▼

State consistency before task closure is ensured by validating that every verification phase has reached completed status, preventing premature closure and enforcing workflow integrity through the Python script.

Does this task closeout workflow require any external dependencies?▼

No external dependencies are required to run this task closeout workflow. It operates independently using a built-in Python workflow script to manage state transitions and generate evidence.

How do I produce auditable evidence for user validation closeout?▼

Auditable evidence for user validation closeout is produced by generating an updated task.json file with state=completed and documenting the associated review notes and verification evidence.

What happens if I try to close user validation before all verification phases are completed?▼

Closing user validation before all phases are completed is blocked by the workflow's state consistency enforcement, which validates that every phase has reached completed status prior to allowing closeout.