test-changed

Execute tests on modules with uncommitted changes in Android or Kotlin Multiplatform projects.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill test-changed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-changed
Source: https://github.com/oscardlfr/AndroidCommonDoc/tree/main/skills/test-changed
Command: npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill test-changed

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the testing process by focusing on modules with uncommitted changes, saving time and resources.

Core Features & Use Cases

  • Selective Testing: Run tests on modules with uncommitted changes, skipping those that are up-to-date.
  • Flexible Options: Offers various parameters to tailor the testing process, such as including shared library changes, specifying test types, and controlling the number of test failures.
  • Use Case: When you want to quickly test only the modules that have been modified since the last commit, use this Skill to execute a focused test suite.

Quick Start

Run tests on changed modules by executing the command: /test-changed

Frequently Asked Questions about test-changed

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

FAQPage Schema
How do I run tests only on changed modules in a Kotlin Multiplatform project?

To run tests only on changed modules in a Kotlin Multiplatform project, execute the `/test-changed` command. This selectively tests modules with uncommitted changes, skipping up-to-date ones to save time and resources.

What is the best way to test uncommitted changes in an Android project?

Testing uncommitted changes in an Android project is best handled by selective testing scripts that identify modified modules. This approach focuses test execution strictly on code with pending changes since the last commit.

Can I include shared library changes when testing modified modules?

Yes, you can include shared library changes when testing modified modules. The Skill provides flexible parameters to tailor the testing process, allowing you to specify test types and control module inclusion.

Does selective testing for changed modules require pre-commit hooks?

Selective testing for changed modules does not require pre-commit hooks, as it directly detects uncommitted changes. However, it is often used alongside pre-commit workflows to validate modifications before finalizing a commit.

How do I control the number of test failures when running tests on changed modules?

You can control the number of test failures when running tests on changed modules by using the Skill's flexible testing parameters. These options allow you to tailor the test suite execution and manage failure thresholds.