Can this skill be used for non-coding tasks?

Yes, it includes a protocol for static assets like documentation and configuration files, verifying accuracy, link resolution, and format compliance.

When should I invoke the Verify skill?

You should use it when you are about to claim a task is done, before a final commit, or when transitioning from code implementation to final reporting.

What is the primary purpose of the Verify skill?

The Verify skill acts as a rigorous quality assurance layer that requires Claude to provide specific evidence (logs, test results, or outputs) before marking any task as complete.

How does this skill handle bug fixes differently?

It includes a dedicated 'FIXED' check that requires documentation of both the pre-fix state (reproduction) and the post-fix resolution to ensure the problem is truly solved.

What happens if a task fails the verification check?

The skill provides a 'NOT COMPLETE' verdict with specific reasons, allowing the agent to address the deficiencies before attempting completion again.

Verify & Validate

Name: Verify & Validate
Author: Jamie-BitFlight

byJamie-BitFlight

•

Security & Testing

Enforces a rigorous verification protocol with evidence-based checklists to ensure tasks are fully completed and validated before submission.

About

The Verify skill implements a structured self-assessment protocol for Claude to use before claiming task completion. By requiring tangible evidence—such as terminal outputs, test results, and before-and-after comparisons—it eliminates guesswork and prevents premature commits. Whether dealing with bug fixes, new features, or documentation updates, this skill ensures that every assertion of 'done' is backed by verifiable data, adhering to the principle that work is only finished when its success can be demonstrated in its intended context.

Key Features

Quality gate integration for linting, type checking, and pre-commit hooks
Automated verification of execution outputs and regression test results
16 GitHub stars
Specific protocols for bug fix validation including reproduction and resolution states
Standardized verification summaries for clear reporting and project tracking
Evidence-based checklists for code, documentation, and configuration files

Use Cases

Verifying documentation accuracy by cross-referencing with actual source code and schemas
Conducting a final 'honesty check' before performing a git commit or merging a feature
Finalizing complex bug fixes to ensure the root cause is addressed without regressions

About

Key Features

Quality gate integration for linting, type checking, and pre-commit hooks
Automated verification of execution outputs and regression test results
16 GitHub stars
Specific protocols for bug fix validation including reproduction and resolution states
Standardized verification summaries for clear reporting and project tracking
Evidence-based checklists for code, documentation, and configuration files

Use Cases

Verifying documentation accuracy by cross-referencing with actual source code and schemas
Conducting a final 'honesty check' before performing a git commit or merging a feature
Finalizing complex bug fixes to ensure the root cause is addressed without regressions