verify

Run modified applications and produce evidence-based verification reports.

3|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/sobird/claude-code --skill verify-sobird
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/sobird/claude-code/tree/main/src/skills/bundled/verify
Command: npx skills add https://github.com/sobird/claude-code --skill verify-sobird

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers need a reliable way to confirm that a code change behaves as intended by running the app and observing outcomes, rather than relying solely on tests.

Core Features & Use Cases

  • End-to-end runtime verification by executing the modified app and capturing observable behavior.
  • Evidence-based reporting that compares observed outcomes with PR claims and helps drive decision-making during reviews.
  • Applicable to PR verification, feature validation, and manual exploratory testing across CLI, server, or UI surfaces.

Quick Start

Run the application with the modified code and record the observable outcomes to validate the change.

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 by running the app instead of relying on tests?

To verify a code change, run the application with the modified code and observe runtime outcomes. This captures observable behavior across CLI, server, or UI surfaces to validate the change.

What is runtime evidence-based reporting for PR review?

Runtime evidence-based reporting executes the modified app and compares observed outcomes with PR claims. It produces a detailed report of steps, observations, and findings to drive decision-making during reviews.

Can I use manual exploratory testing for feature validation across CLI and UI surfaces?

Yes, manual exploratory testing applies to feature validation across CLI, server, and UI surfaces. It requires running the application with the changed code to observe and validate the behavior.

What's the best way to validate that a code change behaves as intended?

The best way to validate code change behavior is executing the modified application and capturing observable outcomes. This produces an evidence-based report comparing observed behavior against PR claims.

Does PR verification work without writing additional automated tests?

Yes, PR verification works without additional automated tests by running the app and observing outcomes. It generates an evidence-based report detailing steps and findings to confirm the change behaves as intended.