skills.rest
luxunxiansheng
luxunxianshengCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run fresh verification commands and validate outputs before claiming completion.

Updated Aug 27, 2026
Search Tags:#verification#evidence#builds#lint#claims#tests#pr-review
One-click install
npx skills add https://github.com/luxunxiansheng/skills2026 --skill verification-before-completion-luxunxiansheng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/luxunxiansheng/skills2026/tree/main/verification-before-completion
Command: npx skills add https://github.com/luxunxiansheng/skills2026 --skill verification-before-completion-luxunxiansheng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams avoid false completion claims by enforcing a verification process: run commands, review outputs, and confirm success only with fresh evidence.

Core Features & Use Cases

  • Verification workflow: Identify the command that proves a claim, execute it fresh, read its output, and verify against success criteria.
  • Evidence-based reporting: Provide explicit evidence when status claims are made, reducing misrepresentations.
  • Use Case: Before merging a PR, run tests, lint, and builds, then only claim success if all checks pass with verifiable output.

Quick Start

Run the full verification sequence by executing the recommended commands and reporting their exact outputs.

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 before claiming a pull request is ready for review?▼

To verify code changes before a pull request, run fresh builds, tests, and lint commands, then assert completion only if the output explicitly meets documented success criteria.

What is evidence-based verification in software development?▼

Evidence-based verification is the process of executing fresh commands and reviewing their exact outputs to prove a status claim, ensuring success is only declared with verifiable fresh evidence.

How do I prevent premature completion claims during software builds?▼

Prevent premature completion claims by enforcing a verification workflow that requires running build commands fresh, validating their outputs, and aligning results with documented success criteria.

What's the best way to ensure linting and tests pass before merging a PR?▼

The best way to ensure linting and tests pass is to execute the full verification sequence and report exact outputs, confirming all checks succeed before making any success claims.

Does automated verification work without manual output validation?▼

No, automated verification requires clear output validation; you must execute fresh command runs and manually confirm the results align with documented verification steps to ensure evidence-based completion.

Related Skills

Explore More Software Engineering Skills→
alex-tgkalex-tgk
1

Verification Before Completion

Execute verification commands to validate tests, lint, and builds before commits.

Community
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
ysyecustysyecust
40

springboot-verification

Verify Spring Boot projects with builds, static analysis, tests, and security scans.

Community
Advanced
yeismeyeisme

verification-before-completion

Verify command output and evidence before claiming code completion.

Community
Advanced