quick-test

Run only tests affected by git diff changes.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/nok0321/claude-pipeline --skill quick-test-nok0321
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-test
Source: https://github.com/nok0321/claude-pipeline/tree/main/skills/quick-test
Command: npx skills add https://github.com/nok0321/claude-pipeline --skill quick-test-nok0321

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically detects modified files via git diff and runs only the tests related to those changes, dramatically speeding up feedback loops.

Core Features & Use Cases

  • Detects changed files and maps them to the relevant test suites for fast validation.
  • Supports pre-commit checks, code reviews, and lightweight validation before commits.
  • Scales across languages and project structures by focusing on impacted tests rather than the entire suite.

Quick Start

Run the quick-test command to automatically execute only tests related to the files modified in your working tree.

Frequently Asked Questions about quick-test

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

FAQPage Schema
How do I run only tests affected by changed files before a git commit?

To run only tests affected by changed files before a git commit, the workflow detects modified files via git diff and maps them to the relevant test suites for fast validation.

What is regression test selection and how does it speed up feedback loops?

Regression test selection speeds up feedback loops by identifying and executing only the tests impacted by the latest code changes, rather than running the entire test suite.

Can I use git diff to map modified files to specific test commands?

Yes, you can use git diff to map modified files to specific test commands. The workflow detects changes via git diff and executes the appropriate test commands with deterministic execution.

Does test selection for pre-commit checks scale across multiple project types?

Test selection for pre-commit checks scales across multiple project types and languages by focusing on impacted tests rather than the entire suite, ensuring lightweight validation before commits.

What is the best way to reduce pre-commit validation time for large codebases?

The best way to reduce pre-commit validation time is to automatically detect modified files and run only the related test suites, providing lightweight validation and faster feedback.

Why should I use impacted test selection instead of running the full test suite?

You should use impacted test selection instead of the full test suite to dramatically speed up feedback loops during pre-commit checks and code reviews by skipping unaffected tests.