How does it handle bug fixes?

It enforces a red-green cycle: first verify the bug fails, then apply the fix, and finally verify the test passes to ensure the fix is genuine.

Why is fresh verification required for every task?

Fresh verification prevents 'hallucinated' success and ensures that the current state of the code actually passes requirements, regardless of previous runs.

What counts as valid verification evidence?

Evidence consists of fresh terminal output, exit codes, and failure counts from relevant tools like test runners, compilers, or linters.

Does this skill help with Pull Request quality?

Yes, by enforcing a 'gate function' before PR creation, it ensures that all claims made in the PR description are backed by verified evidence.

Rigorous Task Verification

Name: Rigorous Task Verification
Author: clsandoval

byclsandoval

0•

Security & Testing

Enforces evidence-based reporting by requiring fresh command execution and output validation before any task is marked as complete.

The Rigorous Task Verification skill acts as a critical gatekeeper for software development workflows, ensuring that Claude never claims success without empirical proof. It mandates a 'verification-before-completion' protocol that requires running fresh tests, builds, or linting commands and confirming the results before any status updates are shared. This approach eliminates the risk of 'hallucinated' success, prevents regressions, and builds high-level trust between the AI and the developer by prioritizing raw output over assumptions or confidence-based assertions.

Key Features

01Identification of 'red flag' language like 'should' or 'probably'

020 GitHub stars

03Mandatory execution of verification commands before status claims

04Comprehensive requirements checklists to prevent missing features

05Red-green regression testing cycles for bug fixes

06Independent verification of agent-delegated sub-tasks

Use Cases

01Validating that bug fixes actually resolve symptoms through regression testing

02Ensuring code is production-ready and linter-clean before opening PRs

03Verifying complex build sequences and dependencies in monorepos

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add clsandoval/monorepo verification-before-completion

For use in Claude.ai and ChatGPT

Key Features

01Identification of 'red flag' language like 'should' or 'probably'

020 GitHub stars

03Mandatory execution of verification commands before status claims

04Comprehensive requirements checklists to prevent missing features

05Red-green regression testing cycles for bug fixes

06Independent verification of agent-delegated sub-tasks

Use Cases

01Validating that bug fixes actually resolve symptoms through regression testing

02Ensuring code is production-ready and linter-clean before opening PRs

03Verifying complex build sequences and dependencies in monorepos

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add clsandoval/monorepo verification-before-completion

For use in Claude.ai and ChatGPT