skills.rest
ingbyr
ingbyrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Require running verification commands and collecting fresh outputs before completion claims.

2|Updated Apr 3, 2026
Search Tags:#verification#governance#evidence#pre-commit#claims#pull-request
One-click install
npx skills add https://github.com/ingbyr/lzcode --skill verification-before-completion-ingbyr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ingbyr/lzcode/tree/main/packages/desktop/src-tauri/lz-assets/skills/verification-before-completion
Command: npx skills add https://github.com/ingbyr/lzcode --skill verification-before-completion-ingbyr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams declare work complete without verification, trust breaks and defects slip through. This skill enforces a clear, evidence-driven claim process.

Core Features & Use Cases

  • Gate on completion: require running verification commands and collecting fresh outputs before declaring success.
  • Evidence-first reporting: present the verification results and attach evidence to PRs or task records.
  • Use Case: before merging a PR or closing a ticket, verify that all tests pass and logs show expected results.

Quick Start

Run the full verification command and attach the resulting evidence before making any success claim.

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 declaring a pull request complete?▼

To enforce verification before declaring a pull request complete, require running verification commands and attaching fresh output evidence to the task context before signaling completion.

What is evidence-based reporting in software governance?▼

Evidence-based reporting in software governance is the process of presenting fresh verification results and attaching command execution outputs to PRs or task records before signaling completion.

How do I validate work status claims against fresh verification evidence?▼

You validate work status claims by running verification commands and collecting fresh output evidence in the task context before allowing any success claims to be made.

Does this verification skill work with pre-commit and release workflows?▼

Yes, this verification skill works with pre-commit, PR, and release workflows by gating completion on running verification commands and collecting fresh evidence before signaling success.

Why do I need fresh evidence before closing a development ticket?▼

You need fresh evidence before closing a development ticket to prevent trust breakdown and defect leakage by verifying that all tests pass and logs show expected results.

What is the best way to gate code completion on passing tests?▼

The best way to gate code completion on passing tests is to require running verification commands and collecting their outputs as evidence before allowing a PR to merge or a ticket to close.

Related Skills

Explore More Software Engineering Skills→
tuantiensiutuantiensiu
1

verification-before-completion

Execute verification commands and collect test, lint, and build evidence before completion claims.

Community
Intermediate
jankneumannjankneumann
4

cleanup-feature

Merge approved pull requests and archive OpenSpec proposals to finalize features.

Community
Advanced
BerryKuipersBerryKuipers
7

commit-with-validation

Create atomic Git commits with standardized messages and pre-commit validation.

Community
Intermediate
miordache93miordache93

monitor-ci

Monitor Nx Cloud CI pipelines and apply automated self-healing fixes.

Community
Advanced