verification-before-completion

Run project verification commands and inspect outputs before marking work complete.

2|Updated Mar 4, 2026

Search Tags:#testing #verification #build #code-quality #lint #gate #self-review

Ready to run

npx skills add https://github.com/thesyntaxninja/syntaxninja-dojo --skill verification-before-completion-thesyntaxninja

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/thesyntaxninja/syntaxninja-dojo/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/thesyntaxninja/syntaxninja-dojo --skill verification-before-completion-thesyntaxninja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature or incorrect completion claims by requiring actionable verification of builds, tests, linters, and project-specific checks so that assertions like "done" or "fixed" are backed by evidence.

Core Features & Use Cases

Gate Enforcement: Treats completion as a gated action that must pass explicit verification before being claimed.
Identify and Run Verifications: Selects appropriate commands for the project (build, lint, test, format checks, or reproduction steps) and requires executing them.
Output Inspection & Recovery: Requires reading full command output for warnings, skipped tests, or partial failures and mandates fixes before proceeding.
Chaining: On successful verification, chains to syntaxninja-dojo:self-review to continue the quality workflow.
Use Cases: Before commit, push, or PR creation; after bug fixes; when handing off work to others; when claiming tests or builds pass.

Quick Start

Run the project's verification commands and confirm all outputs indicate success before marking the task as done.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I verify my code passes build and lint checks before claiming a task is done?▼

Code completion verification requires running project-specific build, lint, and test commands, then inspecting their full output for warnings or partial failures before proceeding. This gated process ensures assertions like "done" or "fixed" are backed by evidence.

What does evidence-first completion verification do for software projects?▼

Evidence-first completion verification treats task completion as a gated action, requiring successful execution of build, test, and lint outputs before allowing a claim of done. It prevents premature completion claims by mandating actionable verification.

When should I run build and test verification commands in my development workflow?▼

Build and test verification should be applied during commits, pull request creation, handoffs, and whenever you state done, fixed, or passing across software projects and configuration changes to ensure work is actually complete.

How do I handle skipped tests or warnings found during pre-commit verification?▼

Pre-commit verification requires reading full command output to identify warnings, skipped tests, or partial failures, and mandates fixing these issues before proceeding to claim the work is complete.

Can I use automated verification gating for configuration changes and bug fixes?▼

Automated verification gating applies to configuration changes and bug fixes by selecting appropriate verification commands, executing them, and requiring all checks to pass before allowing completion claims or chaining to a self-review.

What happens after build and lint verification passes successfully?▼

After successful build and lint verification, the workflow chains to a self-review process to continue the quality workflow, ensuring the verified code undergoes additional review before final completion.