verify

Run tests, validate app behavior, and generate machine-readable verification reports.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill verify-shakhovskiya-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/solo-sdlc/skills/verify
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill verify-shakhovskiya-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying that implemented code actually works by running tests, executing the app, and exercising features to ensure real-world operability before declaring a feature done.

Core Features & Use Cases

  • End-to-end verification: runs tests, starts the app, and exercises acceptance criteria to confirm behavior matches the user story.
  • Verification reporting: emits a machine-readable verification report conforming to schemas/verification-report.schema.json to docs/verification/<task_ref>/<ts>.json and maintains a latest.json symlink for easy discovery.
  • CI/CD integration and DoD alignment: integrates with existing pipelines and feeds liason validators (ai-scrum:dod-validator) to prevent re-running tests unnecessarily.

Quick Start

Run the end-to-end verification workflow to execute tests, run the app, and generate the verification report.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate end-to-end verification of implemented code before review?

End-to-end verification of implemented code automates test execution, validates app behavior, and exercises features to ensure real-world operability before declaring a feature done.

What is the best way to generate a machine-readable verification report for CI/CD?

A machine-readable verification report conforms to schemas/verification-report.schema.json, outputting to docs/verification/<task_ref>/<ts>.json with a latest.json symlink for easy discovery in CI/CD pipelines.

How does end-to-end verification align with the definition of done?

End-to-end verification aligns with the definition of done by feeding liaison validators like ai-scrum:dod-validator, preventing unnecessary test re-runs and confirming acceptance criteria match the user story.

Can I use automated code verification across both libraries and services?

Automated code verification applies across libraries and services in CI/CD, end-to-end feature development, and manual QA handoffs to ensure readiness for review.

What does end-to-end feature verification check during a QA handoff?

End-to-end feature verification during a QA handoff runs tests, starts the app, and exercises acceptance criteria to confirm behavior matches the implemented user story.

Do I need specific dependencies to run the verification workflow?

The verification workflow operates with no external dependencies, requiring only the implemented codebase to run tests, execute the app, and generate the verification report.