skills.rest
alo-exp
alo-expOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforce verification commands and record evidence before commits, PRs, or releases.

6|3|Updated Mar 31, 2026
Search Tags:#qa#completion#governance#evidence#verify#code-review#tests
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill verification-before-completion-alo-exp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/verification-before-completion
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill verification-before-completion-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams claim work is complete without proper checks, this Skill enforces evidence-based completion and prevents premature releases. It ensures verification steps are followed and evidence is captured for auditability.

Core Features & Use Cases

  • Enforces a formal verification workflow before commits, PRs, or releases.
  • Runs and validates verification commands, surfaces results, and records evidence.
  • Use Case: Teams rely on explicit verification to confirm success with objective outputs.

Quick Start

Run the project verification routine and document the output before declaring success.

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 evidence-based verification before claiming a software task is complete?▼

Evidence-based verification before completion requires running explicit verification commands and recording their outputs. This process enforces objective evidence capture, preventing premature claims by validating that tasks pass checks before commits or releases.

What is the best way to prevent unverified code from reaching a pull request or release?▼

Preventing unverified code from reaching a pull request involves enforcing a formal governance workflow. This requires running verification commands, evaluating their outputs, and capturing verifiable evidence to support completion claims before allowing merges or releases.

How do I set up a verification routine that runs tests and records logs before a commit?▼

Setting up a verification routine before a commit involves defining explicit test commands and configuring the workflow to evaluate their outputs. The system then records the emitted logs as verifiable evidence to support and audit the completion claim.

Does this evidence-based completion workflow apply to DevOps environments and release pipelines?▼

Yes, this evidence-based completion workflow applies directly to DevOps environments and release pipelines. It enforces verification steps and captures objective outputs within development workflows, ensuring that tasks are verified with commands and logs before releases.

Why do teams need to verify completion claims with objective command outputs?▼

Teams need to verify completion claims with objective command outputs to prevent premature releases and ensure auditability. Capturing verifiable evidence from tests confirms success explicitly, eliminating unverified assumptions during software development and governance workflows.

Related Skills

Explore More Software Engineering Skills→
oabdelmaksoudoabdelmaksoud
3

verification-loop

Execute build, type check, lint, test, security scan, and diff review.

Community
Advanced
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
PaulKinlanPaulKinlan
2

regression-check

Run full test suites and compare results against a baseline to detect regressions.

Community
Intermediate
LerianStudioLerianStudio
205

dev-validation

Automate development completion validation with acceptance criteria checks and explicit user approval.

Official
Advanced