skills.rest
bgrober
bgroberCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and analyze output before claiming task completion.

1|Updated Jan 7, 2026
Search Tags:#code quality#testing#debugging#verification#completion#process
One-click install
npx skills add https://github.com/bgrober/indie-stack --skill verification-before-completion-bgrober
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/bgrober/indie-stack/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/bgrober/indie-stack --skill verification-before-completion-bgrober

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the premature declaration of work as complete, fixed, or passing by enforcing a strict verification process before any success claims are made.

Core Features & Use Cases

  • Mandatory Verification: Ensures that commands proving completion (e.g., tests, linters, builds) are run and their output is reviewed before any claim of success.
  • Prevents False Positives: Guards against shipping incomplete features, bugs, or broken builds by requiring concrete evidence.
  • Use Case: Before committing code, you must run the test suite and confirm zero failures in the output, not just assume it will pass.

Quick Start

Always run the verification command and check its output before claiming any work is complete.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I prevent false positive claims when verifying code completion?▼

Mandatory verification requires running specific commands like tests, linters, and builds, then analyzing their fresh output to confirm zero failures before claiming any work is complete. This prevents shipping incomplete features.

Why does my code testing process report success before the build is actually finished?▼

Code testing reports premature success when verification is skipped. Enforcing an evidence before claims policy requires running the test suite and confirming zero failures in the actual output, rather than assuming it will pass.

What is the best way to enforce a verification process before reporting task status?▼

The best way to enforce task status verification is applying a strict evidence before claims policy across all development stages. This mandates running verification commands and reviewing their fresh output before asserting any completion, fixing, or passing status.

Does the verification before completion process work with linting and bug fixing?▼

Yes, the verification process applies to all stages of development including linting, building, and bug fixing. It requires running specific verification commands and analyzing their fresh output to confirm success before making any assertions about the work.

When do I need to run verification commands for code quality and debugging?▼

You need to run verification commands for code quality and debugging before committing code or claiming any work is complete. This requires running the test suite and confirming zero failures in the output, rather than assuming it will pass.

Related Skills

Explore More Software Engineering Skills→
sangmokangsangmokang

vcx-dod-gate

Automate Phase 1 DoD gate verification with fresh build, lint, and test evidence.

Community
Advanced
frankxaifrankxai

verification-before-completion

Run verification commands and confirm output before declaring task completion.

Community
Basic
zeronx798zeronx798

requesting-code-review

Scan staged git changes for security issues and quality regressions.

Community
Advanced
enigmaicon-engenigmaicon-eng
1

subagent-driven-development

Execute implementation plans by dispatching fresh subagents per task with two-stage reviews.

Community
Advanced