skills.rest
Mrlyk
MrlykCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Execute verification commands and require evidence before reporting task completion.

4|Updated Apr 5, 2026
Search Tags:#workflow#testing#verification#build#compliance#quality-assurance#code-review
One-click install
npx skills add https://github.com/Mrlyk/superharness --skill verification-before-completion-mrlyk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Mrlyk/superharness/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/Mrlyk/superharness --skill verification-before-completion-mrlyk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents false claims of completion by requiring fresh verification commands and evidence before any success statements, commits, or PRs.

Core Features & Use Cases

  • Gate Function: Enforces a step‑by‑step verification checklist before status updates.
  • Red Flag Detection: Highlights language that implies unverified success.
  • Applicable Scenarios: Used during testing, linting, building, bug fixing, and code reviews to ensure evidence‑backed claims.

Quick Start

Ask the verification-before-completion skill to run the appropriate test command and only then state that the tests pass.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I enforce verification before claiming a software build or code review is complete?▼

Yes, preventing false completion claims requires running fresh build, lint, or test commands and providing their output as evidence. This gates status updates, commits, and pull requests on verified results.

What is the best way to ensure code review status updates are evidence-backed?▼

The best way to ensure evidence-backed status updates is to enforce a verification checklist that examines command output and exit codes. This prevents false completion claims by highlighting red flags in unverified language.

How do I detect red flags in unverified success claims during software development?▼

You detect red flags in unverified success claims by enforcing verification before any work is marked complete. This requires executing test or lint commands and examining their output to provide concrete evidence.

Does this verification workflow require specific testing frameworks to check exit codes?▼

No specific testing frameworks are required. The workflow applies to any software development task where you can execute a verification command and examine its output and exit code to confirm compliance.

When do I need to run verification commands before making a pull request?▼

You need to run verification commands before making a pull request during testing, linting, building, or bug fixing. This ensures your success statements are backed by fresh evidence from the command output.

Related Skills

Explore More Software Engineering Skills→
MolcajeteAIMolcajeteAI
2

post-change-verification

Run Go formatting, linting, building, and testing after code changes.

Official
Advanced
xxihxxih
1

quality-verify

Run verification commands and record results in .quality/quality-check.md.

Community
Intermediate
romiluz13romiluz13
161

build-workflow

Automate software feature builds with TDD and subagent orchestration.

Community
Intermediate
HakiickHakiick

stabilizer

Execute build, test, lint, and type-checking processes for application stability.

Community
Intermediate