skills.rest
DFly7
DFly7COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run full verification commands and attach output evidence before claiming success.

Updated Mar 31, 2026
Search Tags:#testing#verification#build#quality-assurance#code-review#ci#agent-safety
One-click install
npx skills add https://github.com/DFly7/iOS-FastAPI-Supabase-AI --skill verification-before-completion-dfly7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/DFly7/iOS-FastAPI-Supabase-AI/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/DFly7/iOS-FastAPI-Supabase-AI --skill verification-before-completion-dfly7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents false or premature claims of completion, passing tests, or bug fixes by enforcing that the responsible party runs the exact verification commands and produces fresh evidence before asserting success.

Core Features & Use Cases

  • Gate Function: A five-step verification workflow (identify the proving command, run it fully, read full output and exit code, verify evidence, then claim) to stop unverified assertions.
  • Common Scenarios: Use for running test suites, linters, builds, regression cycles, commit/PR readiness checks, and validating agent-reported results.
  • Rationalization Defense: Lists common excuses and red flags to avoid cognitive shortcuts that lead to shipping unverified work.

Quick Start

Before declaring work complete, execute the proving command, inspect the full output and exit code, and report the result with the exact evidence observed.

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 an AI agent from claiming a build or test passes without running it?▼

Verify test results before claiming completion by running the full proving command, inspecting its exit code and output, and ensuring zero failures before asserting any success.

How do I verify test results before claiming completion in a CI workflow?▼

The best way to enforce verification is applying a five-step gate: identify the proving command, run it fully, read the output, verify the evidence, and only then claim completion.

How do I stop false positive claims when running unit tests and linters?▼

Stop false positive claims by executing test suites and linters end-to-end, counting actual failures from the output, and attaching concrete evidence before declaring work done.

Can I use this verification gate for pull request readiness checks?▼

Yes, you can use this verification gate for pull request readiness by requiring fresh evidence from regression checks, builds, and tests before any positive completion claim is made.

What are common red flags to avoid when asserting code review success?▼

Common red flags include cognitive shortcuts and rationalizations that skip executing commands end-to-end, leading to shipping unverified work without examining actual exit codes.

Related Skills

Explore More Software Engineering Skills→
tneztnez

bootstrap

Initialize the .docent directory structure and configuration for new projects.

Community
Basic
tyk-labtyk-lab

verification-before-completion

Run the full verification command and report exit codes and logs.

Community
Intermediate
tilework-techtilework-tech
149

Finishing a Development Branch

Run tests, formatters, linters, type checks, and submit a PR.

Official
Intermediate
RektooooooRektoooooo
2

swift-architecture

Automate Swift code reviews and architecture analysis with static analysis tools.

Community
Intermediate