Code Verify

Require test, linter, and build evidence before finalizing task status.

6|3|Updated Apr 12, 2026

Search Tags:#automation #workflow #testing #quality assurance #code review #verification

Ready to run

npx skills add https://github.com/carson-sweet/sweetclaude --skill code-verify-carson-sweet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Code Verify
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/code-verify
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill code-verify-carson-sweet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill prevents the common pitfall of making premature claims about code completion by enforcing a mandatory, evidence-based verification gate before any work is marked as finished.

Core Features & Use Cases

Evidence-Based Completion: Requires concrete proof (test output, linter results, build logs) before allowing a claim of success.
Standardized Verification: Provides a structured checklist for different claim types, such as bug fixes, regression tests, and requirement fulfillment.
Phase Gate Integration: Ensures that phase transitions are only triggered after all exit criteria have been explicitly validated and documented.

Quick Start

Invoke the code-verify skill to perform a full verification of the current work item and generate an evidence receipt.

Frequently Asked Questions about Code Verify

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

FAQPage Schema

How do I enforce evidence-based code verification before marking a task complete?▼

Enforce evidence-based code verification by requiring explicit execution of test suites, linters, and build commands to generate fresh, objective proof before any work status is finalized.

What is the best way to prevent unverified assertions in software development workflows?▼

Preventing unverified assertions requires a mandatory verification gate that blocks phase transitions until all acceptance criteria are explicitly validated and documented with concrete evidence.

How do I automate code review checks for bug fixes and regression tests?▼

Automate code review checks for bug fixes and regression tests by applying a standardized verification checklist that requires concrete test output and linter results before allowing a claim of success.

Does this verification process require any external dependencies to run test suites and linters?▼

This verification process requires no external dependencies to run test suites and linters, operating as a standalone script component within your existing software engineering workflow.

How do I integrate phase gate checks into a quality assurance workflow?▼

Integrate phase gate checks into quality assurance workflows by ensuring phase transitions are triggered only after all exit criteria have been explicitly validated and documented with fresh evidence.

When should I not use an automated verification gate for code completion claims?▼

Automated verification gates for code completion claims should not be used when you lack executable test suites, linters, or build commands to generate the objective evidence required for validation.