verify

Generate concrete verification plans and execute tests, type checks, and builds.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/jimmi2051/oh-my-copilot --skill verify-jimmi2051
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/jimmi2051/oh-my-copilot/tree/main/plugins/omc-copilot/skills/verify
Command: npx skills add https://github.com/jimmi2051/oh-my-copilot --skill verify-jimmi2051

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that a change really works before you claim completion, by producing concrete evidence rather than vague assertions.

Core Features & Use Cases

  • Turn vague claims into concrete verification plans.
  • Run existing tests, type checks, builds, and manual validation to demonstrate success.
  • Provide clear pass/fail criteria and documented results for audits or reviews.

Quick Start

Create a concrete verification plan for the change and execute the most relevant tests to prove it works.

Frequently Asked Questions about verify

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

FAQPage Schema
What is software change validation and how does it provide verifiable results?

Software change validation confirms that a feature, fix, or refactor works by generating concrete evidence. It runs existing tests, type checks, and builds to produce documented outcomes with clear pass/fail criteria rather than vague assertions.

How do I verify a code change actually works before claiming completion?

To verify a code change, create a concrete verification plan and execute the most relevant tests, type checks, and builds. This demonstrates success through documented outcomes and explicit pass/fail criteria, providing proof that the feature or fix works.

Does build validation work with existing tests and type checks?

Yes, build validation runs your existing tests, type checks, and build processes to demonstrate success. It uses these standard software development workflows to generate verification logs and concrete evidence that your code changes function correctly.

What's the best way to document verification outcomes for a feature refactor?

The best way to document verification outcomes is to establish clear pass/fail criteria upfront, then run tests and manual validation to produce documented results. This turns vague claims into concrete evidence suitable for audits or code reviews.

Can I use manual validation alongside automated tests for change verification?

Yes, change verification supports both automated checks and manual validation. You can run existing tests, type checks, and builds alongside manual validation steps to generate comprehensive evidence that your feature changes work as intended.

Why does my feature verification lack concrete evidence for audits?

Feature verification lacks evidence when relying on vague assertions instead of documented outcomes. By generating a verification plan with explicit pass/fail criteria and running tests, you produce the concrete logs needed for audits or reviews.