verification-before-completion

Require tests, linters, and builds to pass before code commits or PRs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ndriyo/primepm --skill verification-before-completion-ndriyo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ndriyo/primepm/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/ndriyo/primepm --skill verification-before-completion-ndriyo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents dishonest or premature claims of work completion by enforcing strict verification procedures.

Core Features & Use Cases

  • Verification Enforcement: Guides users through running specific verification commands before asserting success.
  • Risk Mitigation: Reduces errors, incomplete features, and unverified code reaching production or code reviews.
  • Use Case: When a developer completes a feature, they use this Skill to confirm all tests pass and build is successful before pushing or opening a PR.

Quick Start

Use the verification-before-completion skill to run your test suite and confirm all tests pass before making a commit.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I enforce verification steps before creating a pull request?

To enforce verification before a pull request, use this Skill to require running tests, linters, and builds with explicit confirmation of successful output before proceeding with code commits.

What is the best way to prevent false success claims during code review?

To prevent false success claims during code review, enforce evidence-based assertions by requiring developers to run validation checks and confirm passing test outputs before finalizing work.

How do I verify code correctness before committing changes?

To verify code correctness before committing changes, this Skill guides you through executing your test suite and build processes, mitigating the risk of unverified code reaching production.

Why do I need to run tests and linters before pushing code?

You need to run tests and linters before pushing code to reduce errors and incomplete features, ensuring strict verification procedures are met and work integrity is maintained before opening PRs.

Can I use this verification process for any software engineering project?

Yes, you can use this verification process for any software engineering project, as it operates as a basic reference component without specific dependencies to enforce validation workflows.