skills.rest
kitfunso
kitfunsoCOMMUNITY
Explore all skills by this author →
Website𝕏@keithso27GitHub

verification-before-completion

Run verification commands and report completion status with evidence.

Updated Apr 9, 2026
Search Tags:#testing#verification#evidence#ci-cd#quality-assurance#claims
One-click install
npx skills add https://github.com/kitfunso/omniskill --skill verification-before-completion-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/kitfunso/omniskill/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/kitfunso/omniskill --skill verification-before-completion-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification is dishonest and risky; this skill enforces evidence-based status reporting to prevent premature success claims.

Core Features & Use Cases

  • Evidence-first verification: run the full verification command and verify outputs before claiming success.
  • Guardrails for PRs and releases: ensures only verified status is communicated to stakeholders.
  • Use Case: when finalizing a feature, run verification to prove tests, lint, and build pass before merging.

Quick Start

Run the full verification commands and review the outputs before making any completion claims.

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 code changes with evidence before claiming a task is complete?▼

To verify code changes with evidence, you must execute the full verification commands, read the outputs, and validate the results before reporting a completion status to stakeholders.

What is evidence-based verification in CI/CD pipelines?▼

Evidence-based verification in CI/CD pipelines is the practice of running full verification commands and validating their outputs to prove builds, tests, and lint results pass before claiming success.

How do I ensure quality assurance before merging a pull request?▼

To ensure quality assurance before merging a pull request, run verification commands to prove that tests, lint, and builds pass, then report the final status with evidence.

Why does claiming work is complete without verification create risk?▼

Claiming work is complete without verification creates risk because it is dishonest and skips evidence-based status reporting, allowing premature success claims that can lead to unverified code changes.

Can I use this approach to prove PR readiness across software projects?▼

Yes, you can use this approach to prove PR readiness across software projects by running full verification commands and validating outputs to ensure only verified status is communicated.

Related Skills

Explore More Software Engineering Skills→
GoldziherGoldziher
115

Task Automation & Build Orchestration

Automate multi-language build, lint, and test workflows with task.

Community
Advanced
ohyesgocoolohyesgocool

ticket-report

Automate Jira ticket reporting and status transitions from merge request coverage.

Community
Advanced
zerAdazerAda

bmad-qa-generate-e2e-tests

Generate end-to-end API and UI tests for identified application features.

Community
Advanced
tizeetizee
2

verification-before-completion

Require fresh verification evidence before declaring code, tests, builds, or tasks complete.

Community
Advanced