verify

Run apps, tests, or scripts to verify code changes and report PASS/FAIL outcomes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/VCasecnikovs/klava --skill verify-vcasecnikovs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/VCasecnikovs/klava/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/VCasecnikovs/klava --skill verify-vcasecnikovs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After code changes, verify they actually work by running the app, tests, or scripts.

Core Features & Use Cases

  • Provides a repeatable workflow to identify changes and verify outcomes across CLI apps, web services, and libraries.
  • Guides you through selecting appropriate verification strategies, executing checks, and validating results.
  • Use cases include feature development, bug fixes, and refactors to ensure changes behave as intended before commit.

Quick Start

Run the verify command with optional args describing what to verify.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify code changes after a bug fix or feature refactor?

Automating code change verification involves detecting git diffs, selecting appropriate verification strategies, and executing checks within timeouts. It reports PASS or FAIL outcomes to ensure your bug fixes, refactors, and features behave as intended across CLI apps, web services, and libraries.

What is the best way to automate testing for git diff analysis?

Automating testing through git diff analysis detects modified code and selects targeted verification strategies. By running specific test suites or scripts based on the identified changes, this approach validates outcomes quickly and reliably without executing the entire test suite.

Can I run targeted checks on web services and CLI tools without executing the full test suite?

Yes, you can run targeted checks on web services and CLI tools by using git diffs to identify modified code. This allows the verification workflow to select and execute only the relevant tests or scripts within defined timeouts, reporting PASS or FAIL outcomes efficiently.

Does automated verification work across different types of projects like libraries and web services?

Automated verification works across libraries, CLI tools, and web services by applying a structured workflow. It detects code changes, selects appropriate verification strategies, executes checks within timeouts, and reports PASS or FAIL outcomes to validate behavior across different project types.

Why does running tests on code changes timeout, and how can I structure verification checks?

Tests on code changes may timeout if verification strategies are not properly structured. By implementing a workflow that selects targeted checks based on git diffs and executes them within defined timeouts, you can prevent timeouts and reliably report PASS or FAIL outcomes.