skills.rest
tridigitals
tridigitalsCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification suites and compare outputs before declaring completion.

Updated Feb 9, 2026
Search Tags:#verification#build#quality-assurance#lint#code-review#continuous-delivery#test-run
One-click install
npx skills add https://github.com/tridigitals/ispmanagement --skill verification-before-completion-tridigitals
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/tridigitals/ispmanagement/tree/main/.roo/skills/verification-before-completion
Command: npx skills add https://github.com/tridigitals/ispmanagement --skill verification-before-completion-tridigitals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before closing a task, merging a PR, or declaring work complete, teams must verify results with fresh evidence. This skill codifies a disciplined verification workflow to prevent dishonest or premature success claims.

Core Features & Use Cases

  • Verification commands: Run a defined set of checks (tests, lint, build) and collect fresh outputs as evidence.
  • Evidence-led completion: Produce a concise verdict pinned to verifiable outputs, not impressions.
  • Use Case: In a code review, require passing verification before marking a PR ready for merge.

Quick Start

Run the designated verification commands on your codebase to produce fresh outputs and attach the results as 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 verify tests and lint checks pass before claiming a PR is ready for merge?▼

Require passing verification before marking a PR ready by running designated checks, collecting fresh outputs, and producing a concise verdict pinned to verifiable outputs rather than impressions.

What is evidence-led completion in continuous delivery?▼

Evidence-led completion prevents premature success claims by requiring fresh verification outputs. You execute a defined set of checks on your codebase and attach the results as evidence to satisfy verification requirements.

How do I stop premature success claims during code reviews?▼

Apply a disciplined verification workflow to code reviews to stop premature success claims. Require fresh evidence from executed test, lint, and build checks before allowing any work to be marked complete.

How do I capture fresh build outputs as evidence for task completion?▼

Capture fresh outputs as evidence by executing a defined set of verification checks on your codebase. This identifies the current state and provides the proof needed to satisfy verification requirements.

Does evidence-led completion work without external continuous delivery dependencies?▼

The verification workflow operates without external dependencies. It identifies the current state by executing a defined set of checks directly on your codebase to capture fresh outputs and produce evidence.

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
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
cxnaivecxnaive

requesting-code-review

Automate pre-commit code verification with static security analysis and regression checks.

Community
Advanced
flexphereflexphere
7

self-review

Automates a three-round self-review workflow for code changes.

Community
Advanced