verification-runner

Execute python3 scripts/workflow.py verify to validate active phases and record evidence.

Updated Mar 7, 2026

Search Tags:#automation #workflow #logging #verification #json #task-management #acceptance

Ready to run

npx skills add https://github.com/alexization/git-ranker-workflow --skill verification-runner-alexization

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Acceptance verification for active phases by executing a standardized workflow and recording evidence in runs/*.json.

Core Features & Use Cases

Execute the acceptance commands for the active phase and confirm it is completed.
Run python3 scripts/workflow.py verify <task-id> to generate verification evidence and keep traceable logs.
Update task.json.latest_run_id and task.json.last_verified_run_id based on verification results; decide next stage.

Quick Start

Run the verification for a given task by executing python3 scripts/workflow.py verify <task-id> after the active phase is completed.

Frequently Asked Questions about verification-runner

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

FAQPage Schema

How do I automate acceptance verification and log evidence for completed tasks?▼

Automate acceptance verification by running python3 scripts/workflow.py verify <task-id>, which validates the active phase and records traceable evidence logs in runs/*.json files for post-completion review.

What is the best way to update task status and track the latest verified run in a JSON workflow?▼

Updating task status is handled automatically during verification by writing the latest_run_id and last_verified_run_id fields into task.json, ensuring the most recent verification results are traceable.

How do I execute a standardized verification workflow after a development phase is finished?▼

Execute a standardized verification workflow by running the verify command against the specific task-id once the active phase is completed, generating output logs to track runs history and status updates.

When do I need to run post-completion verification across tasks and runs history?▼

Post-completion verification is needed when an active phase has finished acceptance and requires standardized validation across tasks, runs history, and status updates to confirm successful completion and record evidence.

Does the verification workflow require any external dependencies to generate JSON evidence logs?▼

The verification workflow requires no external dependencies to generate JSON evidence logs, relying solely on python3 to execute the workflow script and update the task management files with verification results.

Why is verification-runner not updating the last_verified_run_id field in task.json?▼

The last_verified_run_id field in task.json fails to update if the active phase has not properly finished acceptance, as the verification workflow strictly requires post-completion status before executing and recording evidence.