verification-before-completion

Require fresh verification evidence before reporting task completion.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/fartmonarch/RenderMind --skill verification-before-completion-fartmonarch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/fartmonarch/RenderMind/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/fartmonarch/RenderMind --skill verification-before-completion-fartmonarch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of success by requiring fresh verification evidence before you say work is done, tests passed, or a fix is complete.

Core Features & Use Cases

  • Evidence-first validation: Run the relevant command, read the full output, and confirm the result before making any positive claim.
  • Completion gatekeeping: Use it before marking tasks finished, creating pull requests, or handing work to another agent.
  • Use Case: After fixing a bug, you rerun the affected tests and only report the issue as resolved when the output clearly shows success.

Quick Start

Before declaring any task complete, rerun the most relevant verification command and only state success if the output directly supports it.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I prevent unsupported claims of completion when fixing bugs?

To prevent unsupported claims of completion when fixing bugs, enforce fresh verification by rerunning the affected tests and only reporting success when the output explicitly confirms it.

What is evidence-first build validation before creating a pull request?

Evidence-first build validation before creating a pull request is the process of running the full validation command, reading the output, and confirming the exit status before marking any task finished.

How do I verify a build passed before reporting task completion?

To verify a build passed before reporting task completion, run the relevant validation command, check for failures in the output, and base every positive claim on explicit evidence from that fresh run.

Can I use completion gatekeeping for handoffs between agents?

Yes, you can use completion gatekeeping for handoffs between agents by requiring the upstream agent to rerun verification commands and provide explicit proof of success before transferring the workflow.

Why does reporting success without checking exit status cause workflow issues?

Reporting success without checking exit status causes workflow issues because it allows premature claims of completion, leading to unverified bug fixes and failed builds progressing into downstream pull requests.