How does it handle testing for full-stack apps?

The protocol enforces a 'Full Test Suite' rule, requiring backend unit tests, frontend component tests, E2E flows, and API contract validation before approval.

When is the mandatory time to use this skill?

This skill is mandatory before every git commit, before creating a pull request, and before marking any feature as complete to ensure professional-grade quality.

Does this skill help with documentation?

Yes, it includes a dedicated Documentation Verification step that checks for PHPDoc/JSDoc, README updates, CHANGELOG entries, and API documentation.

What happens if a test fails during verification?

The skill instructs you to stop immediately, fix the failed tests, and restart the verification protocol before any code can be committed or handed off.

Verification Before Completion

Name: Verification Before Completion
Author: liauw-media

byliauw-media

Security & Testing

Enforces a rigorous multi-step quality checklist to verify functionality, tests, and documentation before any code is committed or finalized.

About

The Verification Before Completion skill acts as a mandatory quality gate for the development lifecycle, ensuring that no task is marked 'done' without thorough validation. It provides a structured protocol that covers requirements tracing, end-to-end testing, integration checks, and documentation audits. By enforcing these 'Iron Laws' before every git commit or pull request, the skill prevents regressions, broken builds, and undocumented features, maintaining a professional standard of code quality and team reliability.

Key Features

Automated documentation audits for READMEs, CHANGELOGs, and API docs
Mandatory pre-commit checklist to prevent broken builds and regressions
Comprehensive 10-step verification protocol for features and bug fixes
Standardized verification reporting for clear stakeholder handoffs
0 GitHub stars
Cross-stack validation for frontend, backend, and API integrations

Use Cases

Performing a final quality audit before opening a pull request to main branches
Ensuring 100% test coverage and documentation updates before a production release
Verifying full-stack features where frontend and backend changes must remain in sync

About

Key Features

Automated documentation audits for READMEs, CHANGELOGs, and API docs
Mandatory pre-commit checklist to prevent broken builds and regressions
Comprehensive 10-step verification protocol for features and bug fixes
Standardized verification reporting for clear stakeholder handoffs
0 GitHub stars
Cross-stack validation for frontend, backend, and API integrations

Use Cases

Performing a final quality audit before opening a pull request to main branches
Ensuring 100% test coverage and documentation updates before a production release
Verifying full-stack features where frontend and backend changes must remain in sync