nobody-verifies-before-completion

Run verification commands and analyze output before claiming task completion.

36|1|Updated Feb 12, 2026

Search Tags:#testing #quality assurance #debugging #verification #completion

Ready to run

npx skills add https://github.com/HashWarlock/nobody-plans-for-pi --skill nobody-verifies-before-completion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nobody-verifies-before-completion
Source: https://github.com/HashWarlock/nobody-plans-for-pi/tree/main/skills/nobody-verifies-before-completion
Command: npx skills add https://github.com/HashWarlock/nobody-plans-for-pi --skill nobody-verifies-before-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of task completion by enforcing a strict verification process before any success assertion is made.

Core Features & Use Cases

Mandatory Verification: Ensures that evidence is gathered and reviewed before declaring a task as done, fixed, or passing.
Failure Identification: Helps identify common pitfalls and rationalizations that lead to incomplete or inaccurate status reports.
Use Case: Before reporting that a bug fix is complete, this Skill ensures the relevant test command is run and its output confirms the fix, preventing false positives.

Quick Start

Always run the verification command and check its output before claiming any status.

Frequently Asked Questions about nobody-verifies-before-completion

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

FAQPage Schema

How do I enforce verification before claiming a bug fix is complete?▼

To enforce verification before claiming completion, you must run specific test commands and analyze their full output to confirm the fix actually works. This prevents false positives and ensures accuracy in status reporting.

Why does task completion verification fail without checking command output?▼

Task completion verification fails without checking command output because there is no evidence to confirm the bug fix or test passing. Analyzing the full command output prevents dishonesty and identifies common pitfalls or rationalizations.

What is the best way to prevent false positives when reporting a passing test?▼

The best way to prevent false positives when reporting a passing test is to apply a strict verification protocol that requires running the relevant test command and confirming the success status directly in its output.

Can I use this verification process for general operational tasks beyond debugging?▼

Yes, you can use this verification process for general operational tasks beyond debugging. It applies to all development and operational tasks requiring confirmation of success before any status assertion is made.

How do I identify common pitfalls that lead to inaccurate task status reports?▼

To identify common pitfalls that lead to inaccurate task status reports, you must review the gathered evidence and command outputs against the original claims. This strict verification exposes rationalizations that lead to incomplete status updates.