verify-before-complete

Name: verify-before-complete
Availability: InStock
Author: Jason

Enforce completion gates requiring linting, tests, and browser smoke checks.

Updated May 11, 2026

Search Tags:#governance #handoff #baseline #verify #quality-check #completion-gate #ui-smoke

Ready to run

npx skills add https://github.com/jason660519/Project-Manager --skill verify-before-complete-jason660519

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-before-complete
Source: https://github.com/jason660519/Project-Manager/tree/main/.agents/skills/verify-before-complete
Command: npx skills add https://github.com/jason660519/Project-Manager --skill verify-before-complete-jason660519

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This solution enforces a mandatory completion gate for software projects, preventing teams from marking a feature as done until all required checks have passed, ensuring quality and readiness before release.

Core Features & Use Cases

Automated baseline verification: runs a sequence of checks (linting, type checks, tests) to validate the codebase.
Manual browser smoke: requires UI checks in a real browser to confirm usability before claiming completion.
Governance and handoff: provides a clear protocol for commit/PR readiness and marks progress only after gates pass.

Quick Start

Start by integrating this skill to enforce baseline verification and UI smoke checks before marking a feature complete.

Frequently Asked Questions about verify-before-complete

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

FAQPage Schema

How do I prevent declaring a feature complete until all code quality checks pass?▼

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.

What manual browser smoke checks are needed before a PR handoff?▼

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.

How do I set up a completion gate for automated baseline verification?▼

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.

Does this completion gate work for both UI and backend feature workflows?▼

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.

What's the best way to enforce governance and quality-checks before a commit?▼

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.

Why should I run verify:baseline instead of just marking a feature as done?▼

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.