evidence-review

Verify test outputs, build logs, and screenshots before shipping features.

13|4|Updated Feb 20, 2026

Search Tags:#testing #screenshots #verification #quality #evidence #ci #build-logs

Ready to run

npx skills add https://github.com/OmexIT/claude-skills-pack --skill evidence-review-omexit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evidence-review
Source: https://github.com/OmexIT/claude-skills-pack/tree/main/skills/evidence-review
Command: npx skills add https://github.com/OmexIT/claude-skills-pack --skill evidence-review-omexit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides an objective, verifiable gate to ensure only proven quality passes to release by demanding evidence for every claim.

Core Features & Use Cases

Systematic evidence collection across tests, builds, and UI verification to validate claims.
Reproducible review workflow that you can re-run to confirm results.
Use Case: When releasing a feature, attach test outputs, logs, and screenshots to prove readiness.

Quick Start

Run the verification workflow against the target codebase to collect test outputs, logs, and screenshots for evidence.

Frequently Asked Questions about evidence-review

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

FAQPage Schema

What is evidence-based verification for software release readiness?▼

Evidence-based verification is a quality gate that enforces systematic collection of test outputs, build logs, and screenshots to prove feature readiness. It ensures all P0 verification evidence is present and validated before shipping.

How do I enforce test output and build log verification in CI before merging a PR?▼

Run the verification workflow against your target codebase to collect test outputs, build logs, and screenshots. This enforces a reproducible quality gate that validates P0 evidence and provides remediation guidance for any failures.

Can I use this evidence review workflow for feature implementations and final reviews?▼

Yes, the workflow handles cross-cutting verification across feature PRs, implementations, and final reviews. It systematically collects and validates evidence to enforce a rigorous quality gate before shipping software features.

What's the best way to verify UI changes with screenshots during a PR review?▼

The best way is using a systematic evidence collection workflow that captures screenshots alongside test outputs and build logs. This provides an objective, reproducible verification process that proves UI readiness with clear pass/fail criteria.

Does this verification workflow run without external dependencies?▼

Yes, the evidence verification workflow operates without external dependencies. It functions as a standalone quality gate that systematically collects and validates test outputs, build logs, and screenshots directly from your target codebase.

Why does my feature review fail when test outputs are missing?▼

Your review fails because the evidence-based quality gate enforces that all P0 verification evidence, including test outputs, must be present and validated. The workflow provides remediation guidance to help you collect and attach the missing evidence.