test-runner

Run relevant tests before Git commits and block failed ones.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/elmisi/claude-code-automation --skill test-runner-elmisi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-runner
Source: https://github.com/elmisi/claude-code-automation/tree/main/plugin/templates
Command: npx skills add https://github.com/elmisi/claude-code-automation --skill test-runner-elmisi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Ensures code quality and stability by automatically running relevant tests before code changes are committed, preventing regressions and enforcing standards.

Core Features & Use Cases

  • Guaranteed Test Execution: Prevents commits if tests fail, ensuring a stable codebase.
  • Intelligent Test Selection: Dynamically chooses which tests to run based on changed files, optimizing CI/CD pipelines.
  • Use Case: Automatically run only the unit tests related to modified files during a Git commit, blocking the commit if any of those tests fail.

Quick Start

Use the test-runner skill to run tests before every commit.

Frequently Asked Questions about test-runner

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

FAQPage Schema
How do I automate tests to run before every Git commit?

Automating tests before a Git commit requires a pre-commit hook that triggers test execution and blocks the commit if tests fail. This enforces a pass-fail gate to prevent unstable code from entering the codebase.

Can I run only the tests related to my changed files instead of the full test suite?

Yes, intelligent test selection dynamically chooses which tests to run based on file changes. This optimizes your CI/CD pipeline by executing only the unit tests related to modified files during a commit.

What do I need to set up to block Git commits when tests fail?

To block Git commits when tests fail, you need integration with Git hooks and a test execution framework. The hook enforces a pass-fail gate that prevents committing code that causes regressions.

How does a pre-commit hook improve code quality and CI/CD automation?

A pre-commit hook improves code quality by automatically running relevant tests before changes are committed, preventing regressions. This local automation optimizes downstream CI/CD pipelines by catching failures early.

Does this intelligent test selection work with my existing test execution framework?

Intelligent test selection requires integration with a test execution framework and Git hooks. It triggers your existing framework to run dynamically selected tests based on changed files before a commit proceeds.