skills.rest
mraakashshah
mraakashshahCOMMUNITY
Explore all skills by this author →
Website𝕏@aakashdotioGitHub

verification-before-completion

Run verification commands before claiming software work is complete.

5|Updated Feb 7, 2026
Search Tags:#software engineering#quality assurance#code review#verification#work completion
One-click install
npx skills add https://github.com/mraakashshah/oro --skill verification-before-completion-mraakashshah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/mraakashshah/oro/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/mraakashshah/oro --skill verification-before-completion-mraakashshah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent dishonesty by ensuring that work is verified before it is claimed as complete, fixed, or passing.

Core Features & Use Cases

  • Verification Commands: Provides templates for verification commands for different programming languages.
  • Gate Function: Outlines a structured process for verification before making any claims.
  • Common Failures: Lists common pitfalls to avoid during verification.
  • Rationalization Prevention: Offers guidance against common rationalizations for skipping verification.
  • Key Patterns: Suggests ways to communicate verification results clearly.

Quick Start

Run the verification commands before claiming any work is complete.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I ensure code is verified before claiming work completion?▼

To ensure code is verified before work completion, you must execute specific verification commands and review the results before making any claims that a task is fixed or passing. This process acts as a quality gate against dishonest reporting.

What are common rationalizations to avoid when skipping code review verification?▼

Common rationalizations for skipping code review verification include assuming minor changes are safe or trusting previous test runs. Avoiding these pitfalls requires a structured gate function to prevent claiming work is complete without manual verification.

How do I run verification commands for different programming languages?▼

Run verification commands for different programming languages by using the provided templates specific to your environment. This manual execution ensures your software development workflow maintains quality assurance before completion is claimed.

What is the best way to communicate code verification results clearly?▼

The best way to communicate code verification results is by using suggested key patterns to report outcomes clearly. This ensures honesty in your software engineering workflow by documenting exactly what was tested and confirmed.

Does manual verification prevent dishonesty in software development workflows?▼

Manual verification prevents dishonesty in software development workflows by requiring developers to execute commands and observe results before claiming work is complete. This gate function ensures quality assurance and accurate work completion reporting.

Related Skills

Explore More Software Engineering Skills→
leifericfleifericf
5

verify-lanes

Execute predefined shell commands to verify project code lanes and report results.

Community
Intermediate
mt-krainskimt-krainski
1

wrap

Automate branch completion with code review, linting, testing, commits, and Pull Request creation.

Community
Advanced
lastcowlastcow

innozverse-testing-quality

Enforce linting, type checking, formatting, and build checks for the innozverse project.

Community
Intermediate
GrassHopper42GrassHopper42

ios-fix

Detect, repair, and verify iOS bugs in CI/CD pipelines.

Community
Advanced