verification

Enforce fresh verification evidence before completion claims in WordPress/PHP projects.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/iwritec0de/wp-dev --skill verification-iwritec0de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/iwritec0de/wp-dev/tree/main/skills/verification
Command: npx skills add https://github.com/iwritec0de/wp-dev --skill verification-iwritec0de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WordPress/PHP projects often proceed to completion without verifiable evidence. This skill enforces a gate that requires fresh verification outputs before any completion claim, commit, or PR.

Core Features & Use Cases

  • Fresh evidence gating: enforces verification before claims of completion.
  • Structured verification workflow: defines commands, outputs, and reporting steps to ensure reproducibility.
  • Real-world applicability: suitable for any WP/PHP project requiring reliable quality checks prior to release.

Quick Start

Run the verification gate to produce fresh evidence before claiming task completion.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I enforce fresh verification evidence before a WordPress commit or pull request?

To enforce fresh verification evidence before a WordPress commit or pull request, run a defined command set of unit tests, coding-standards checks, and environment checks. This gate reads command outputs to confirm success before allowing completion claims.

What is the best way to ensure verifiable progress in PHP projects during CI/CD workflows?

The best way to ensure verifiable progress in PHP projects during CI/CD workflows is to implement a structured verification gate. This requires executing PHPUnit tests and PHPCS checks to produce fresh evidence before approving status reports or releases.

Does this verification gate work with PHPUnit and PHPCS for WordPress code quality checks?

Yes, this verification gate works with PHPUnit and PHPCS for WordPress code quality checks. It executes these specific commands during commits and pull requests to read outputs and confirm successful coding-standards compliance.

Can I use this structured verification workflow to block completion claims without fresh test outputs?

Yes, you can use this structured verification workflow to block completion claims without fresh test outputs. It enforces a strict gate that requires running unit tests and environment checks, ensuring no task proceeds without verifiable evidence.

Why do WordPress projects proceed to completion without verifiable evidence, and how can I stop it?

WordPress projects often proceed to completion without verifiable evidence due to missing quality gates. You can stop this by enforcing a verification gate that reads PHPUnit and PHPCS outputs to confirm success before any commit, PR, or status report.

When do I need to run environment checks for PHP coding standards and unit tests?

You need to run environment checks for PHP coding standards and unit tests during commits, pull requests, and status reports. This structured workflow ensures reproducibility and confirms successful verifiable progress prior to any completion claim.