Radberi-VerificationBeforeCompletion

Guide users to run verification commands and confirm task success.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/primeBeri/huml-dotnet --skill radberi-verificationbeforecompletion-primeberi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Radberi-VerificationBeforeCompletion
Source: https://github.com/primeBeri/huml-dotnet/tree/main/.claude/skills/Radberi-VerificationBeforeCompletion
Command: npx skills add https://github.com/primeBeri/huml-dotnet --skill radberi-verificationbeforecompletion-primeberi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the tendency to claim task completion prematurely without proper verification, which can lead to errors, unverified results, and misinformation.

Core Features & Use Cases

  • Verification Workflow Enforcement: Guides users through executing commands, reviewing outputs, and confirming results before making success claims.
  • Best Practice Reminders: Highlights common pitfalls like trusting unverified agent reports or partial checks.
  • Use Case: A developer wants to ensure their tests have passed before pushing code, and uses this Skill to confirm outputs and verify test success, ensuring no false positives.

Quick Start

Use the verification skill to check that all tests are passing before creating a pull request.

Frequently Asked Questions about Radberi-VerificationBeforeCompletion

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

FAQPage Schema
How do I verify tests pass before claiming task completion?

Run verification commands and analyze their outputs to confirm task success, preventing premature completion claims. This enforces a validation workflow that reviews results before pushing code or creating a pull request.

What is verification before completion in quality assurance?

Verification before completion is a best practice that enforces running validation commands and reviewing outputs to confirm task success, preventing unverified results and misinformation from premature completion claims.

Why does claiming task completion prematurely cause errors?

Claiming task completion prematurely causes errors because it relies on unverified agent reports or partial checks, leading to unvalidated results and misinformation instead of properly confirmed test outputs.

What's the best way to enforce a validation workflow for code changes?

The best way to enforce a validation workflow is to systematically execute verification commands, review their outputs, and confirm positive results before pushing code, ensuring no false positives slip through.

Do I need to run specific commands to validate task success?

Yes, you need to run specific verification commands and analyze their outputs to validate task success, ensuring you do not trust unverified agent reports or partial checks before claiming completion.