verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: SteamedFish

Run verification commands and review output before claiming task completion.

6|Updated Jan 14, 2020

Search Tags:#code quality #testing #ci/cd #verification #evidence #assertions

Ready to run

npx skills add https://github.com/SteamedFish/dotfiles --skill verification-before-completion-steamedfish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/SteamedFish/dotfiles/tree/main/.config/opencode/skills/superpowers/verification-before-completion
Command: npx skills add https://github.com/SteamedFish/dotfiles --skill verification-before-completion-steamedfish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents premature claims of completion or success by enforcing a strict verification process before any assertion is made, ensuring accuracy and preventing costly mistakes.

Core Features & Use Cases

Mandatory Verification: Ensures that claims of passing tests, clean linters, successful builds, or fixed bugs are backed by fresh, executed verification commands.
Evidence-Based Assertions: Promotes a culture of "evidence before claims," requiring concrete output from verification tools before any success statement is made.
Use Case: Before committing code, you must run shellcheck on your script and confirm zero errors in its output, preventing the introduction of syntactical bugs.

Quick Start

Always run the verification command and check its output before stating that work is complete.

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 running tests before claiming code completion?▼

To enforce running tests before claiming code completion, this Skill mandates executing verification commands like linters or build tools to produce fresh evidence, preventing premature assertions of success or correctness in your development workflow.

What is evidence-based verification in CI/CD pipelines?▼

Evidence-based verification in CI/CD pipelines is a process requiring concrete output from verification tools before any success statement is made. It ensures claims of passing tests, clean linters, or successful builds are always backed by fresh command execution results.

How do I prevent premature assertions of fixed bugs and successful builds?▼

You prevent premature assertions of fixed bugs and successful builds by enforcing a rigorous verification process that mandates the execution and review of specific commands to produce fresh evidence before any claims of task completion or correctness are made.

Does this verification process work with standard linters and build tools?▼

Yes, this verification process works with standard linters and build tools. It mandates executing specific commands like shellcheck to confirm zero errors in the output, ensuring your code meets defined criteria before you state that work is complete.

What are the limitations of relying on manual code quality checks?▼

Relying on manual code quality checks risks unverified code, incomplete features, and broken builds. This Skill addresses these limitations by requiring concrete output from verification tools, ensuring work meets defined criteria before any success statement is made.