quick-test

Run targeted Jest tests for files changed since the last Git commit.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SS2608-dev/Resilience --skill quick-test-ss2608-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-test
Source: https://github.com/SS2608-dev/Resilience/tree/main/.claude/skills/dev/quick-test
Command: npx skills add https://github.com/SS2608-dev/Resilience --skill quick-test-ss2608-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly run only the tests relevant to their recent code changes, significantly speeding up the development feedback loop.

Core Features & Use Cases

  • Targeted Test Execution: Identifies and runs tests associated with modified files.
  • Efficient Debugging: Reduces the time spent waiting for the full test suite to complete.
  • Use Case: After making a small change to a component, use this Skill to run only the tests for that specific component instead of the entire project's test suite.

Quick Start

Use the quick-test skill to run tests for files changed since the last commit.

Frequently Asked Questions about quick-test

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

FAQPage Schema
How do I run Jest tests for only the files changed in my recent Git commits?

Run targeted Jest tests for modified files by analyzing Git diff output to identify changed code and execute only the corresponding test suites, reducing feedback cycle time during active development.

What is the best way to speed up unit and end-to-end test execution during debugging?

Speed up test execution by targeting only unit and end-to-end tests associated with recent code modifications, allowing developers to skip waiting for the full test suite to complete during debugging sessions.

Do I need Git and Jest configured to run targeted tests on recent code modifications?

Yes, you need both Git and Jest configured in your project, as Git identifies the changed files through diff analysis and Jest executes the corresponding targeted test suites for those modifications.

How does automated targeted test execution identify which test suites to run?

Automated targeted test execution identifies relevant suites by using Git diff to track recent code modifications, then mapping those changed files to their corresponding Jest tests for rapid feedback.

Can I use this targeted testing approach for continuous integration workflows?

Yes, targeted testing integrates into CI workflows by using Git diff to run only tests for modified files, ensuring rapid feedback cycles during active coding and automated continuous integration processes.

When should I avoid running targeted tests and execute the full test suite instead?

Avoid targeted tests when verifying global application stability or before final deployment, as running only tests for modified files may miss regressions in unrelated modules that a full test suite would catch.