test

Executes specified tests and commands and reports verdicts with evidence.

113|15|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/avibebuilder/claude-prime --skill test-avibebuilder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/test
Command: npx skills add https://github.com/avibebuilder/claude-prime --skill test-avibebuilder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a disciplined, repeatable process for verifying whether a runtime claim holds by executing tests or commands and returning a clear verdict backed by captured evidence. It prevents ambiguous "looks right" answers by insisting on concrete commands, exit codes, output, and suite statistics so stakeholders get an objective result.

Core Features & Use Cases

  • Automated Verification Flow: Define the claim, scope the verification, select the correct execution lane, run the tests or commands, and produce a standardized Verification Report.
  • Pre-flight and Safety Checks: Validates infra requirements and refuses to start servers or mutate shared state; instructs users exactly what must be running before verification.
  • Evidence-first Reporting: Produces a structured report with Claim, Verdict, Evidence, Failures, Gaps, and Suite Stats suitable for CI checks, reviewer handoffs, or tester teammates.
  • Team Isolation Guidance: Includes a tester handoff pattern to spawn isolated teammates for unbiased execution when needed.

Quick Start

Run the specified test or command and produce a Verification Report that states the claim, verdict, evidence, failures, gaps, and suite stats.

Frequently Asked Questions about test

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

FAQPage Schema
How do I run tests and generate an evidence-backed verification report for a CI check?

Run tests and generate an evidence-backed verification report by defining the claim, scoping verification, selecting an execution lane, and capturing exact commands, exit codes, output, and suite statistics for an objective verdict.

What is evidence-based test verification and when do I need it for unit or integration tests?

Evidence-based test verification is the process of executing tests and producing a structured report with a verdict, evidence, failures, and gaps. It is needed for unit, integration, API, frontend, and backend scenarios requiring objective runtime confirmation.

How do I verify a runtime claim holds without debugging or reviewing the code?

Verify a runtime claim by applying the automated verification flow to execute the specified tests and deliver a standardized report. The report states the claim, verdict, evidence, failures, gaps, and suite stats without debugging or reviewing code.

What is the best way to capture test exit codes and suite statistics for a tester handoff?

The best way to capture test exit codes and suite statistics is using a structured verification report. It enables tester handoffs by providing isolated execution patterns and standardized evidence suitable for CI checks and reviewer handoffs.

What are the limitations of automated test verification for shared state infrastructure?

Limitations include refusing to start required infrastructure or mutate shared state during verification. The process validates infra requirements upfront and stops if dependencies are missing, requiring you to manually run necessary servers before executing tests.