Verified:GitHub

checklist-runner

Validate work against Markdown checklists and produce approval decisions.

Updated May 6, 2025

Search Tags:#code review #quality gate #definition of done #test results #git diff #checklist validation #markdown workflows

Ready to run

npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill checklist-runner-rodrigo-altissimo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checklist-runner
Source: https://github.com/rodrigo-altissimo/qiartificial/tree/main/.claude/skills/checklist-runner
Command: npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill checklist-runner-rodrigo-altissimo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The checklist-runner Skill removes ambiguity in quality gates by systematically checking a change or output against a defined Markdown checklist, so teams can reliably approve or request fixes.

Core Features & Use Cases

Automated checklist validation: Executes any .md checklist with consistent PASS/FAIL/PARTIAL/N/A verdicts and per-item evidence reasoning.
YOLO and interactive review modes: Runs autonomously for fast assessment or prompts section-by-section for human confirmation.
Context-aware evidence loading: Collects story files, code files, test results, and git diff context as specified by the checklist.
Use cases: Definition-of-Done checks for stories, pre-push quality gates, release readiness, and PO validation/change impact review.

Quick Start

Run the checklist in YOLO mode by invoking: checklist-runner pre-push-checklist --mode yolo.

Frequently Asked Questions about checklist-runner

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

FAQPage Schema

How do I automate a Definition of Done check using a Markdown checklist?▼

To automate a Definition of Done check, you validate work against a specified Markdown checklist to produce a structured approval decision. The process yields consistent PASS, FAIL, PARTIAL, or N/A verdicts with per-item evidence reasoning.

What is the best way to enforce a pre-push quality gate with code review and test results?▼

Enforcing a pre-push quality gate involves running a checklist validation that collects git diff context, code files, and test results. This systematically checks your changes against defined criteria to compute pass rates and explicit fix recommendations.

Can I run checklist validation autonomously without manual confirmation?▼

Yes, you can run checklist validation autonomously using deterministic YOLO mode. This mode executes the entire Markdown checklist without human intervention, while an alternative interactive mode prompts section-by-section for manual confirmation.

How does a Markdown checklist validation process gather evidence for a release readiness review?▼

Checklist validation gathers evidence for release readiness through context-aware loading. It automatically collects story files, code files, test results, and git diff context as specified by the Markdown checklist to support per-item verdicts.

When do I need an interactive section-by-section review for PO validation?▼

You need an interactive section-by-section review for PO validation when assessing change impact requires human confirmation. This mode prompts reviewers sequentially through checklist sections to ensure accurate validation of complex evidence.