C✳CODEZ.WIN
🌐 English

Localized reading guide

verification-before-completionPurpose, usage and source

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Source retrieved:

Source repository
obra/superpowers
SKILL.md
skills/verification-before-completion/SKILL.md
Repository stars
309,479
Repository updated
2026-10-30
Categories
Agent workflows
Last collected

License: MIT

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

How the upstream workflow works

Overview

Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit of this rule.

Upstream passage · L8 ↗

When To Apply

ANY variation of success/completion claims ANY expression of satisfaction ANY positive statement about work state Committing, PR creation, task completion

Upstream passage · L106 ↗

The Iron Law

If you haven't run the verification command in this message, you cannot claim it passes.

Upstream passage · L14 ↗
Upstream passage · ↗
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2ce8aa15d05bd57213e6f746f953aafb7ded7a8b
Source SHA-256
2befe7fc55bcadaa3d97dd9e8efeb633d2561c0ebe74c5a8b17c4d9e7e4520b3
Back to the full Skill catalog