test

Add or update tests and run the smallest relevant Gradle test task.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/YeaChan05/Remittance --skill test-yeachan05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/test
Command: npx skills add https://github.com/YeaChan05/Remittance --skill test-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The job of the skill is to help teams add or update repository-style tests and run the smallest relevant Gradle test task to validate changes without performing full code reviews or release handoffs.

Core Features & Use Cases

  • Identify the closest existing test pattern and adapt it for the change
  • Implement minimal test changes within the same scope to prove behavior
  • Run the smallest Gradle test command to generate focused evidence of correctness

Quick Start

Run the smallest relevant Gradle test task for the affected module to verify the work.

Frequently Asked Questions about test

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

FAQPage Schema
How do I add unit tests for a bug fix without running the entire Gradle suite?

To add unit tests for a bug fix, identify the nearest existing test pattern, implement minimal changes within that scope, and execute only the smallest relevant Gradle test task to produce focused proof of correctness.

What is the best way to update integration tests during a code refactor?

The best way to update integration tests during a refactor is to adapt the closest existing test pattern, implement minimal test changes to prove behavior, and run the smallest Gradle test command for evidence without needing a full code review.

Can I run a focused Gradle test task to verify quick feature changes?

Yes, you can run a focused Gradle test task to verify quick feature changes by identifying the nearest test pattern, implementing minimal test updates within that scope, and executing only the smallest relevant Gradle command to generate proof.

Does this approach work for repository-style projects that need minimal test updates?

Yes, this approach works for repository-style projects by adding or updating tests with minimal scope, adapting the closest existing test pattern, and running the smallest Gradle test task to validate changes without performing full release handoffs.

Why run only the smallest Gradle test command instead of the full build?

Running only the smallest Gradle test command instead of the full build generates focused evidence of correctness quickly, which is ideal for bug fixes, feature changes, or refactors where full code reviews or release handoffs are unnecessary.

When should I avoid using minimal test updates for refactoring?

You should avoid minimal test updates for refactoring when full code reviews or release handoffs are required, as this approach is designed to run only the smallest relevant Gradle test task for quick evidence rather than comprehensive validation.