skills.rest
chronista-club
chronista-clubOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verification

Execute commands and validate output before claiming task completion.

Updated Dec 20, 2025
Search Tags:#testing#quality assurance#verification#completion#discipline#evidence
One-click install
npx skills add https://github.com/chronista-club/claude-plugin-chronista-style --skill verification-chronista-club
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/chronista-club/claude-plugin-chronista-style/tree/main/verification
Command: npx skills add https://github.com/chronista-club/claude-plugin-chronista-style --skill verification-chronista-club

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the premature declaration of task completion by enforcing a rigorous verification process, ensuring that claims are backed by evidence and preventing "hallucinated" or unverified outcomes.

Core Features & Use Cases

  • Evidence-Based Claims: Mandates the execution of specific commands and the review of their output before any assertion of success or completion.
  • Reduces False Positives: Catches errors, incomplete tests, or failed builds that might otherwise be overlooked.
  • Use Case: Before committing code, running pytest and verifying that all tests pass with zero failures, then using the output as proof of a successful test run.

Quick Start

Execute the verification process for the current task.

Frequently Asked Questions about verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes before claiming task completion?▼

Verify code changes before claiming completion by executing relevant test commands, thoroughly reviewing their output, and validating the results against your assertions to ensure evidence-backed success.

What is an evidence-based verification protocol in software engineering?▼

An evidence-based verification protocol mandates running specific commands and reviewing their output to prove task success, preventing premature completion claims and reducing false positives from unverified outcomes.

How do I prevent premature declarations of task completion during development?▼

Prevent premature completion declarations by enforcing a strict verification process that requires executing commands, reviewing test output, and validating outcomes against assertions before any success is claimed.

Does this verification protocol work across all stages of development?▼

Yes, this verification protocol applies to all stages of development and task management where a definitive outcome must be proven, ensuring claims are backed by concrete execution evidence.

Why does my testing process overlook failed builds and incomplete tests?▼

Your testing process likely overlooks failed builds because it lacks a strict verification protocol that mandates executing commands and validating output against assertions before declaring success.

Related Skills

Explore More Software Engineering Skills→
CripacxCripacx

verification-before-completion

Verify command output and exit codes before declaring task completion.

Community
Basic
ShiienShiien
7

code-commit

Stage files, run tests, and commit with a standardized prefix and diff summary.

Community
Advanced
adriannoesadriannoes
46

verification-before-completion

Execute verification commands and confirm outputs meet success criteria.

Community
Intermediate
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate