verify-before-complete

Enforce a completion gate to prevent declaring feature completion until baseline verification, manual browser smoke testing, and governance checks pass. This gating process ensures codebase quality and UI readiness before marking any task as 100% complete.

Before a PR handoff, manual UI smoke checks in a real browser are required to confirm usability and UI readiness. This ensures the interface behaves correctly and satisfies the governance protocol for verifiable feature handoff.

Automated baseline verification runs a sequence of checks including linting, type checks, and tests to validate the codebase. Integrating this skill enforces those checks, running commands like npm run verify:baseline before allowing commit or PR readiness.

Yes, the completion gate applies to development workflows across both UI and backend features. It enforces baseline verification and manual UI smoke checks, ensuring verifiable handoff and compliance across different types of software projects.

The best way to enforce governance before a commit is applying a gating process that marks progress only after automated linting, tests, and compliance checks pass. This provides a clear protocol for commit readiness and prevents incomplete features from shipping.

Running verify:baseline prevents marking a feature as done until all required checks pass, ensuring quality and readiness. It validates the codebase through linting, type checks, and tests, providing a verifiable handoff protocol before release.