skills.rest
Renzo-Tognella
Renzo-TognellaCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Verify work completion by running commands and checking outputs before claiming success.

Updated Apr 26, 2026
Search Tags:#code review#verification#evidence-based claims#commit process#work completion
One-click install
npx skills add https://github.com/Renzo-Tognella/UniversalThingsForMyAgents --skill verification-before-completion-renzo-tognella
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Renzo-Tognella/UniversalThingsForMyAgents/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/Renzo-Tognella/UniversalThingsForMyAgents --skill verification-before-completion-renzo-tognella

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The problem addressed is the lack of evidence-based claims in work completion, leading to potential inaccuracies and trust issues.

Core Features & Use Cases

  • Evidence-Based Claims: Ensures that any claim of work completion is backed by fresh verification evidence.
  • Verification Process: Provides a structured gate function for verification, including identifying, running, reading, verifying, and only then making claims.
  • Use Case: Before committing code, developers can use this skill to run verification commands, check outputs, and confirm that the work meets the required standards.

Quick Start

Run the verification commands for your work and confirm the output before making any success claims.

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 making a commit?▼

Verifying code before a commit requires running verification commands, reading the output, and confirming standards are met before claiming completion. This structured process prevents inaccurate claims.

What is an evidence-based claim in the code review process?▼

An evidence-based claim means no work completion is stated without fresh verification evidence. It requires executing commands and verifying their output to back any success claim.

How do I ensure work completion claims are backed by verification evidence?▼

Ensuring work completion claims are backed by evidence requires a structured gate: identify verification commands, run them, read the output, verify correctness, and only then make the claim.

Can I use this verification process for pull requests and task completions?▼

Yes, you can use this verification process for pull requests and task completions. It applies to any task requiring evidence of completion, ensuring claims are supported by fresh command output.

What's the best way to prevent inaccurate claims during the commit process?▼

The best way to prevent inaccurate claims during the commit process is to require fresh verification evidence. A structured gate function ensures developers run commands and verify outputs before claiming success.

Related Skills

Explore More Software Engineering Skills→
pur3v4d3rpur3v4d3r
6

verification-before-completion

Run verification and attach fresh output before claiming completion.

Community
Advanced
kubuszokkubuszok
6

verified-merge

Merges GitHub pull requests while preserving users' verified commit signatures.

Official
Advanced
burgebjburgebj

ios-fix

Automate detection, repair, and verification of iOS bugs.

Community
Advanced
rsmdtrsmdt
381

specification-compliance

Validate implementations against documented specifications with structured compliance reporting.

Community
Advanced