skills.rest
shichengwuyu
shichengwuyuCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run full verification commands and attach output evidence before marking work complete.

4|1|Updated Apr 11, 2026
Search Tags:#verification#evidence#pr#quality-assurance#code-review#claims#build-verification
One-click install
npx skills add https://github.com/shichengwuyu/PaiJiPlus --skill verification-before-completion-shichengwuyu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/shichengwuyu/PaiJiPlus/tree/main/.trae/skills/verification-before-completion
Command: npx skills add https://github.com/shichengwuyu/PaiJiPlus --skill verification-before-completion-shichengwuyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Step-based verification: identify the proving command, run it in full, read the output, and verify the result before claiming completion.
  • Applicable to code changes, tests, builds, and PR readiness to ensure trustworthy outcomes.
  • Use Case: before merging a PR, run all verification steps and attach evidence to the PR description.

Quick Start

Run the full verification sequence and attach outputs as evidence before declaring completion.

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 marking a PR as complete?▼

To verify code changes before marking a PR as complete, you must identify and execute the relevant proving commands, read the output, and validate the results to produce fresh evidence for every claim. This prevents premature success declarations.

What is the best way to ensure claims in a pull request are backed by evidence?▼

The best way to ensure claims in a pull request are backed by evidence is to run a full verification sequence across repositories and attach the fresh command outputs directly to the PR description as proof of readiness.

How does build verification prevent premature success declarations?▼

Build verification prevents premature success declarations by enforcing a step-based method where you run full verification commands, read the outputs, validate the results, and report outcomes with attached evidence before claiming completion.

Can I apply quality assurance verification steps to both tests and code builds?▼

Yes, you can apply quality assurance verification steps to both tests and code builds. The method identifies the proving command, runs it in full, reads the output, and verifies the result to ensure trustworthy outcomes across repositories.

When do I need to run full verification commands and attach outputs as evidence?▼

You need to run full verification commands and attach outputs as evidence before merging a PR, declaring task completion, or making any claims regarding code changes, tests, or builds to ensure every claim is backed by fresh results.

Related Skills

Explore More Software Engineering Skills→
jr2804jr2804

verification-before-completion

Execute verification commands and analyze outputs before asserting completion.

Community
Basic
ilderajilderaj

verification-before-completion

Run verification commands and require fresh evidence before completion claims.

Community
Advanced
ZuixiZuixi
1

verification-before-completion

Run explicit verification commands and review outputs before declaring task completion.

Community
Intermediate
primeBeriprimeBeri
1

Radberi-VerificationBeforeCompletion

Guide users to run verification commands and confirm task success.

Community
Basic