skills.rest
maraxen
maraxenCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and report completion only with fresh evidence.

4|1|Updated Apr 4, 2024
Search Tags:#verification#evidence#ci-cd#quality-assurance#claims#tests
One-click install
npx skills add https://github.com/maraxen/praxis --skill verification-before-completion-maraxen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/maraxen/praxis/tree/main/.agent/skills/verification-before-completion
Command: npx skills add https://github.com/maraxen/praxis --skill verification-before-completion-maraxen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that any claim of completion is backed by fresh verification evidence, preventing premature success statements.

Core Features & Use Cases

  • Enforces a structured verification workflow: identify the verification command, execute it fully, read the output, verify results, and report with evidence.
  • Applicable to development and review workflows to avoid misrepresenting the state of work, including tests, lint checks, builds, and PR approvals.

Quick Start

Run the full verification command, review the output, and only claim success when fresh verification evidence is produced.

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 premature completion claims in CI/CD pipelines?▼

Prevent premature completion claims by enforcing a structured verification workflow that runs full verification commands, validates outputs, and reports success only when fresh verification evidence is produced.

What is verification evidence in software development?▼

Verification evidence in software development is the fresh output from executed commands like tests, lint checks, or builds, used to validate results and prove work is actually complete before merging.

How to verify build outputs before claiming a task is complete?▼

Verify build outputs before claiming completion by identifying the specific verification command, executing it fully, reading the output to confirm results, and reporting the status with supporting evidence.

Do I need to run tests before claiming a pull request is ready for review?▼

Yes, claiming a pull request is ready for review requires running verification commands like tests and lint checks to completion, validating outputs, and reporting success with fresh evidence.

What's the best way to enforce quality assurance checks before merging code?▼

The best way to enforce quality assurance checks before merging code is to apply a structured workflow that requires running tests and builds, verifying the outputs, and reporting with fresh evidence.

Why does my code review workflow fail to catch incomplete features?▼

Code review workflows fail to catch incomplete features when success statements are made prematurely without enforcing the execution of verification commands and validating fresh output evidence.

Related Skills

Explore More Software Engineering Skills→
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
cornmanwtfcornmanwtf

compliance-evidence-pack

Assemble compliance evidence, system logs, and audit artifacts for security audits.

Community
Intermediate
choub00choub00

verification-loop

Automate build, type, lint, test, and security checks across code sessions.

Community
Advanced
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate