skills.rest
mrtolkien
mrtolkienCOMMUNITY
Explore all skills by this author →
Website𝕏@tolkicastsGitHub

verification

Run verification commands and confirm fresh evidence before declaring task completion.

5|Updated Feb 24, 2026
Search Tags:#validation#qa#verification#evidence#quality-assurance#guardrails#claims
One-click install
npx skills add https://github.com/mrtolkien/GHOST --skill verification-mrtolkien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/mrtolkien/GHOST/tree/main/prompts/skills/superpowers/verification
Command: npx skills add https://github.com/mrtolkien/GHOST --skill verification-mrtolkien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce verification before declaring task completion, preventing unverified success claims and reducing risky releases.

Core Features & Use Cases

  • Verification workflow enforcement: guides users to identify the verification command, run it freshly, read the output, and verify results before declaring completion.
  • Evidence-first claims: requires presenting fresh verification evidence to support status updates.
  • Guardrails for automation: blocks automated success reports from bypassing formal checks in CI or release pipelines.

Quick Start

Execute the verification checklist on a pending task to ensure fresh evidence is obtained before claiming completion.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I enforce verification before declaring a task complete in software development?▼

Evidence-first verification requires obtaining fresh output from a verification command before declaring task completion. This workflow prevents unverified success claims and reduces risky releases in software development and QA pipelines.

What is evidence-first completion verification in QA workflows?▼

Evidence-first verification is a formal QA procedure requiring fresh verification output to support task completion claims. It blocks automated success reports from bypassing formal checks by ensuring code changes are proven complete with new evidence.

How do I stop automated success reports from bypassing CI checks?▼

Implement guardrails that require fresh verification evidence before any status update to stop automated reports from bypassing CI checks. This formal procedure identifies the verification command, runs it, and validates the output before claiming success.

What's the best way to verify code changes are actually complete before release?▼

Apply a formal verification checklist to verify code changes are complete: identify the specific verification command, run it freshly, read the output, and verify the results. Only then can you confidently declare task success.

Can I use verification guardrails for quality assurance in existing release pipelines?▼

Yes, verification guardrails apply to software development and QA workflows within existing CI or release pipelines. They enforce fresh evidence collection from verification steps, blocking automated success reports from bypassing formal quality-assurance checks.

Related Skills

Explore More Software Engineering Skills→
J-PsterJ-Pster
291

verification-before-completion

Enforces fresh verification evidence before allowing completion claims in builds, tests, lints, or migrations.

Community
Advanced
The-AIOSThe-AIOS
15

verification-before-completion

Execute verification commands and confirm outputs before claiming task completion.

Official
Intermediate
LerianStudioLerianStudio
205

dev-feedback-loop

Automate development-cycle metrics collection and generate improvement reports.

Official
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced