checklist-runner

To validate code changes against a Definition of Done checklist, you can run a markdown checklist validation tool against your repository evidence and test artifacts to produce a consistent APPROVED or FAIL acceptance decision.

Yes, you can automate pre-push quality gate checks by running a markdown checklist in autonomous yolo mode to generate per-section pass rates and an overall acceptance decision without manual step-by-step confirmation.

Evidence-based checklist validation works by loading story, source, test, and git diff context, then matching each markdown checklist item to supporting repository evidence to determine if release readiness criteria are met.

Yes, checklist validation supports interactive mode for step-by-step confirmations, allowing you to manually verify each checklist item against code and test artifacts instead of running fully autonomous checks.

The best way to enforce code quality gates before merging is to execute a markdown checklist validation that thresholds pass rates and evaluates criticality to output an overall NEEDS_WORK or APPROVED decision.

You can resolve a checklist file by its name using optional fuzzy matching, allowing the validation process to locate and execute the correct markdown checklist without requiring the exact file path.