skills.rest
JaimeJunr
JaimeJunrCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and report evidence before claiming task completion.

2|Updated Apr 11, 2026
Search Tags:#validation#verification#evidence#quality-assurance#code-review#software-engineering#pr-checklist
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill verification-before-completion-jaimejunr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill verification-before-completion-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without verification is dishonest and risky, potentially releasing unverified code or failing features.

Core Features & Use Cases

  • Enforces a verification-first workflow before declaring success across development tasks (tests, builds, PRs).
  • Guides users to identify the verification command, run it afresh, assess the results, and attach evidence when reporting outcomes.
  • Use case: before merging a PR, run the required checks and only claim completion if verification passes with a verifiable log.

Quick Start

Execute the full verification command, review the outcome, and only then claim completion with supporting evidence.

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 code completion?▼

To enforce verification before claiming code completion, execute the required verification command, evaluate the output, and only report success if the results pass with attached evidence.

What is a PR readiness checklist and why does it need evidence?▼

A PR readiness checklist ensures code validation before merging by requiring developers to run tests and builds, attaching verifiable logs as evidence to prove all checks pass successfully.

How do I run build and test results validation before a pull request merge?▼

To run build and test results validation before a pull request merge, identify the verification command, run it afresh, assess the outcome, and report actual results rather than assuming success.

Can I use this verification-first workflow for any software engineering task?▼

Yes, the verification-first workflow applies to any software engineering task requiring validation, including pull request readiness, build verification, and test result assessment before declaring success.

What is the best way to prevent claiming completion without verified test results?▼

The best way to prevent claiming completion without verified test results is to execute the full verification command, review the actual outcome, and only claim success with supporting evidence.

Why does claiming completion without verification cause issues in code review?▼

Claiming completion without verification causes issues in code review because it risks releasing unverified code or failing features, making the assertion dishonest and potentially harmful to software quality.

Related Skills

Explore More Software Engineering Skills→
edwinhuedwinhu
19

dev-worktree

Create an isolated Git worktree with dependency setup and test verification.

Community
Advanced
managedcodemanagedcode
4

mcaf-code-review

Audit pull request readiness for code, tests, and documentation.

Official
Intermediate
jfrometajfrometa

lint-and-validate

Run lint, type checks, and security audits on Node.js and Python projects.

Community
Advanced
XGanQAQXGanQAQ
1

smoke-check

Run automated smoke tests and generate PASS/FAIL gate reports.

Community
Advanced