skills.rest
brainworkup
brainworkupCOMMUNITY
Explore all skills by this author →
Website𝕏@brainworkupGitHub

verification-before-completion

Require fresh test, lint, or build evidence before declaring task completion.

1|Updated Apr 8, 2026
Search Tags:#verification#evidence#claims#ci#tests#pr-review
One-click install
npx skills add https://github.com/brainworkup/skills --skill verification-before-completion-brainworkup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/brainworkup/skills/tree/main/neuropsych-reports/references/luria-related-complement-skills/verification-before-completion
Command: npx skills add https://github.com/brainworkup/skills --skill verification-before-completion-brainworkup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This rule prevents dishonest success claims by enforcing fresh verification evidence before asserting completion, PR status, or deployment readiness.

Core Features & Use Cases

  • Enforces a step-by-step verification gate for code changes, builds, tests, and lint checks.
  • Guides teams in validating outputs and documenting evidence before declaring success.
  • Useful for PR reviews, releases, and task handoffs to ensure verifiable results.

Quick Start

Run the verification workflow on your latest changes and report the final verified status.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I prevent unverified completion claims in PR reviews?▼

To prevent unverified completion claims in PR reviews, enforce a step-by-step verification gate requiring fresh test outputs, lint results, and build status before declaring success. This ensures claims are backed by evidence rather than assumptions.

What is a verification gate for code changes and task workflows?▼

A verification gate for code changes is a mandatory checkpoint requiring fresh verification evidence, such as running full test commands and inspecting outputs, before any success claim is asserted or a task workflow is marked complete.

How do I require fresh test outputs before asserting deployment readiness?▼

To require fresh test outputs before asserting deployment readiness, run the full verification command on your latest changes, inspect the results, and only declare success after documenting the fresh test, lint, and build evidence.

Does this verification workflow work without external dependencies?▼

Yes, this verification workflow works without external dependencies. It provides an Advanced standalone rule set to guide teams in validating outputs and documenting evidence directly within existing code changes and task workflows.

When do I need to enforce evidence before declaring task completion?▼

You need to enforce evidence before declaring task completion during PR reviews, releases, and task handoffs to prevent dishonest success claims and ensure all code changes are backed by verifiable test, lint, and build results.

Related Skills

Explore More Content & Communication Skills→
GolferGeekGolferGeek

Quality Gates

Run npm lint, format, test, and build before commits.

Community
Advanced
rodrigobranasrodrigobranas
1

verification-before-completion

Enforces fresh verification before allowing claims of completion in PRs and builds.

Community
Intermediate
thomfilgthomfilg

follow-up

Monitor CI builds, handle PR reviews, and apply suggested fixes.

Community
Advanced
hanibalskhanibalsk
3

verification-before-completion

Run verification commands and require evidence before completion claims.

Community
Basic