test

Automates full-project verification suite runs and reports PASS/FAIL statuses without modifying code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to run the project's full verification suite and obtain a structured health report without applying any fixes.

Core Features & Use Cases

  • Read-only verification: executes typecheck, lint, tests, and build commands and reports results without altering code.
  • Baseline validation: ideal for CI red, post-merge, or pre-PRD checks to confirm a clean baseline.
  • Structured output: returns a concise summary suitable for dashboards or pipelines.

Quick Start

Run the skill to execute the project's verify commands (typecheck, lint, tests, build) and report a structured summary without applying fixes.

Frequently Asked Questions about test

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

FAQPage Schema
How do I run a read-only verification suite for typecheck, lint, tests, and build in CI?

Run a read-only verification suite to execute typecheck, lint, tests, and build commands, returning a structured per-command summary and a final PASS/FAIL status without applying any code fixes.

Can I validate a clean baseline for CI health checks before a PRD without modifying code?

You can validate a clean baseline for CI health checks or pre-PRD checks by running the verification suite in read-only mode, which reports typecheck, lint, tests, and build results without altering your code.

What is the best way to automate post-merge verification and report results for a pipeline?

Automate post-merge verification by running the full verify suite, which discovers commands from common configurations, executes them in a defined order, and returns a concise structured summary suitable for dashboards or pipelines.

Does the verification suite discover commands automatically or do I need to configure them manually?

The verification suite discovers commands from common configurations automatically, runs them in a defined order, and outputs a per-command summary, eliminating the need for manual command configuration.

Why does my CI health check report a FAIL status without applying fixes to the code?

A CI health check reports a FAIL status because the read-only verification suite executes typecheck, lint, tests, and build commands to validate the baseline without applying any fixes, leaving code unaltered.