skills.rest
leonardoteodoroo
leonardoteodorooCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run fresh verification commands and validate outputs before claiming completion.

Updated Feb 3, 2026
Search Tags:#verification#completion#build#evidence#pull-request#tests
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill verification-before-completion-leonardoteodoroo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/verification-before-completion
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill verification-before-completion-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy helps teams avoid making unverified completion claims by enforcing fresh verification before stating success, thereby reducing risk of miscommunication and low-quality releases.

Core Features & Use Cases

  • Enforces a formal verification gate before updating work status (tests, builds, lint, or other verifications).
  • Guides who, when, and how to collect evidence and report outcomes for PRs, releases, or task handoffs.
  • Provides a repeatable workflow that can be integrated into CI pipelines or manual checks to ensure honesty and traceability.

Quick Start

Run the verification command in your workflow and report the observed outcome with supporting 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 build and test completion before claiming a pull request is ready?▼

To verify pull request completion, execute fresh build and test commands, read the outputs, and validate outcomes before updating work status. This enforces a verification gate to ensure traceability and reduce miscommunication in PR workflows.

What is fresh verification evidence in a CI pipeline?▼

Fresh verification evidence is the output collected from executing tests, builds, or lint checks immediately before stating success. It provides observed outcomes and supporting proof to enforce honesty and traceability across releases.

How do I enforce a verification gate for lint checks and regression checks?▼

Enforce a verification gate by identifying the specific command, running it fresh, reading the results, and verifying the outcomes. Only after this process is complete can you claim success for lint or regression checks.

Can I integrate completion verification into manual checks and PR workflows?▼

Yes, this verification process provides a repeatable workflow that integrates into CI pipelines or manual checks. It guides who, when, and how to collect evidence and report outcomes for PRs, releases, or task handoffs.

Why does my build completion claim fail during regression checks?▼

Build completion claims fail when success is stated without executing fresh verification commands and validating their outputs. Without a verification gate to collect evidence, unverified claims risk miscommunication and low-quality releases.

Related Skills

Explore More Software Engineering Skills→
joekhosbayarjoekhosbayar

gds-test-review

Analyze test results and coverage to generate a structured test-review report.

Community
Intermediate
softwaresaltsoftwaresalt
1

operational-closure

Generate dated closure markdown files with monitoring and rollback plans.

Community
Advanced
cxnaivecxnaive

requesting-code-review

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

Community
Advanced
iliaaliliaal
30

ia-verification-before-completion

Require fresh verification evidence before reporting task completion.

Community
Advanced