verify

Verify code changes by running tests and reporting pass/fail evidence.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Pryma-Tech/iris --skill verify-pryma-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/Pryma-Tech/iris/tree/main/cli/skills/verify
Command: npx skills add https://github.com/Pryma-Tech/iris --skill verify-pryma-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and verify that a code change actually works by producing concrete evidence.

Core Features & Use Cases

  • Provide a structured verification workflow for features, fixes, or refactors.
  • Capture and report what was verified, the commands/tests run, and the outcomes to prevent misleading claims.

Quick Start

Describe the change you want verified and request evidence of validation.

Frequently Asked Questions about verify

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

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

To verify a code change, document the exact validation steps, run existing tests or typechecks, and report pass/fail status with concrete observable evidence like build outputs or test results.

What is the best way to document verification steps for a feature or refactor?

Documenting verification steps involves recording the commands executed, the tests run, and the observable outcomes, ensuring that feature, fix, or refactor changes are corroborated with proof.

Can I use this for manual validation of fixes, or is it only for automated testing?

You can use this for manual validation, automated testing, and builds, as it applies to any software development workflow where changes must be corroborated with observable outcomes.

Why should I produce concrete evidence when testing code changes?

Producing concrete evidence when testing code changes prevents misleading claims by capturing and reporting what was verified, the commands run, and the actual pass/fail outcomes.

How do I structure a verification workflow for a software fix?

Structure a verification workflow by describing the change, defining exact validation steps, running existing tests or typechecks, and reporting the pass/fail status alongside the captured evidence.