smart-test-runner

Detect modified files via git status and run targeted tests with run-tests.ps1.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/dezverev/AnimalAL-v1 --skill smart-test-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-test-runner
Source: https://github.com/dezverev/AnimalAL-v1/tree/main/.cursor/skills/smart-test-runner
Command: npx skills add https://github.com/dezverev/AnimalAL-v1 --skill smart-test-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates targeted test execution for IntegrationTesterApp by inferring relevant tests from code changes and the current workspace context, reducing wasted test runs.

Core Features & Use Cases

  • Auto-detect test scope from git status and recent modifications to Plugins and Kernel code.
  • Map changes to test tags and invoke run-tests.ps1 with precise -t filters, minimizing build time.
  • Generate concise failure reports and integrate with CLAUDE.md workflow to guide fixes.

Quick Start

Use the smart-test-runner to execute tests based on the current context. For example, say: run tests, run stock tests, or test weather,geolocation.

Frequently Asked Questions about smart-test-runner

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

FAQPage Schema
How do I run targeted tests based on git status changes?

Targeted test execution uses git status to detect modified files and maps those changes to relevant test tags. It then invokes run-tests.ps1 with appropriate -t filters to minimize build time and reduce wasted test runs.

Can I specify explicit test tags instead of relying on auto-detection?

Explicit test tags are fully supported alongside auto-detection. You can directly specify tags like "weather,geolocation" to run-tests.ps1, overriding context inference to execute precise test suites for IntegrationTesterApp.

How does context-aware test filtering work for PowerShell test runners?

Context-aware test filtering analyzes recent modifications to Plugins and Kernel code via git status. It maps the detected file changes to specific test tags, passing precise -t filters to the PowerShell runner to execute only relevant tests.

Do I need a specific CI environment to automate IntegrationTesterApp test runs?

A CI environment is not strictly required. The smart-test-runner integrates with CLAUDE.md workflows and executes local PowerShell scripts, detecting modified files via git status to automate targeted test runs in any workspace.

What is the best way to generate concise failure reports for targeted test runs?

Concise failure reports are generated automatically after executing targeted test runs. The runner highlights failures from the filtered run-tests.ps1 output, integrating with CLAUDE.md workflows to guide subsequent code fixes.

Why run filtered test tags instead of the full IntegrationTesterApp test suite?

Running filtered test tags minimizes build time by executing only tests relevant to your current code changes. This context-aware approach avoids wasted test runs and provides faster feedback on failures.