harness-test-advisor

Identify minimal test sets from changed files with graph-aware discovery and static fallbacks.

18|11|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-test-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-test-advisor
Source: https://github.com/Intense-Visions/harness-engineering/tree/main/agents/skills/claude-code/harness-test-advisor
Command: npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-test-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identifies the minimal, high-value set of tests to run after code changes to accelerate feedback loops and CI cycles.

Core Features & Use Cases

  • Graph-aware test discovery when a repository graph exists, with deterministic fallbacks to static analysis if the graph is missing.
  • Tiered test prioritization (Must Run, Should Run, Could Run) to optimize CI time and local development turnaround.
  • Generates quick-run and full-run commands and reports coverage gaps for changed files.

Quick Start

Provide a list of changed files or a diff to trigger an analysis and generate test run commands.

Frequently Asked Questions about harness-test-advisor

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

FAQPage Schema
How do I select the minimal set of tests to run for changed files?

Test selection for changed files applies graph-driven discovery to identify a minimal, high-coverage test set, gracefully falling back to static analysis and naming-convention strategies when a repository graph is unavailable.

How do I prioritize tests to improve CI efficiency after code changes?

To improve CI efficiency, test prioritization categorizes results into Must Run, Should Run, and Could Run tiers, generating quick-run and full-run commands to optimize feedback loops and CI cycles.

Does test selection work without a repository graph?

Test selection works without a repository graph by gracefully falling back to static analysis and naming-convention strategies to determine the relevant tests for your changed files.

How do I find test coverage gaps for changed files?

Finding test coverage gaps for changed files is handled during the analysis process, flagging missing tests and delivering a structured tiered result for CI and local development workflows.

What is graph-driven test discovery for CI efficiency?

Graph-driven test discovery for CI efficiency is a mechanism that analyzes a repository graph to identify the exact tests impacted by changed files, ensuring high coverage while running only necessary tests.