Grails Test Fixer
apache/grails-core
Guides running, reviewing and fixing test failures across grails-core modules with Gradle, including targeted runs and the aggregate HTML and Markdown reports.
Run a Gradle project's tests by test type or module — unit, integration, or all.
Install Run Tests
$ npx skills add Amplicode/spring-skills --skill run-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Amplicode/spring-skills run-tests --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Amplicode/spring-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/run-tests .claude/skills/run-tests && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "run-tests" agent skill from https://github.com/Amplicode/spring-skills/tree/main/skills/run-tests into .claude/skills/run-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-tests", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Amplicode/spring-skills/tree/main/skills/run-testsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Amplicode/spring-skills --skill run-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Amplicode/spring-skills run-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Amplicode/spring-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/run-tests .agents/skills/run-tests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "run-tests" agent skill from https://github.com/Amplicode/spring-skills/tree/main/skills/run-tests into .agents/skills/run-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-tests", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Amplicode/spring-skills --skill run-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Amplicode/spring-skills run-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Amplicode/spring-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/run-tests .cursor/skills/run-tests && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "run-tests" agent skill from https://github.com/Amplicode/spring-skills/tree/main/skills/run-tests into .cursor/skills/run-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-tests", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Amplicode/spring-skills.git --path skills/run-tests--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Amplicode/spring-skills --skill run-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Amplicode/spring-skills run-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Amplicode/spring-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/run-tests .gemini/skills/run-tests && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "run-tests" agent skill from https://github.com/Amplicode/spring-skills/tree/main/skills/run-tests into .gemini/skills/run-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-tests", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Amplicode/spring-skills run-testsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Amplicode/spring-skills --skill run-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Amplicode/spring-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/run-tests .github/skills/run-tests && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "run-tests" agent skill from https://github.com/Amplicode/spring-skills/tree/main/skills/run-tests into .github/skills/run-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-tests", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Amplicode/spring-skills --skill run-tests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Amplicode/spring-skills run-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Amplicode/spring-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/run-tests .opencode/skills/run-tests && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "run-tests" agent skill from https://github.com/Amplicode/spring-skills/tree/main/skills/run-tests into .opencode/skills/run-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-tests", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
run-tests- GitHub stars
- 126
- Token cost
- ~432 tokens
- SKILL.md length
- 196 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- None found
At a glance
Run a Gradle project's tests by test type or module — unit, integration, or all.
- The user wants to run
- SKILL.md covers Test types and modules and Pick the path
- Check the projects tests (e.g
What it does
Run Tests is an agent skill from Amplicode/spring-skills. Run a Gradle project's tests by test type or module — unit, integration, or all. Use this skill whenever the user wants to run, re-run, or check the project's tests (e.g. "run the unit tests", "run all tests", "run the integration tests for the vet module", "did the tests pass?").
Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/gradle.md`, `references/ide.md` and `references/report.md`).
It sits in Testing & QA, covering Integration testing and Unit testing. It works with Gradle. The repository describes itself as: Amplicode Agent Tools.
When your agent uses it
- The user wants to run
- Check the projects tests (e.g
Example prompts
- “s tests (e.g.”
- “run all tests”
- “run the integration tests for the vet module”
- “/run-tests”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit bf19b3c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Run Tests loads about 432 tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 196 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 196 words (~432 tokens).
“Test types (extend as a project needs):”
- name
- run-tests
Files
SKILL.md and 4 other files (scripts, references) in skills/run-tests of Amplicode/spring-skills.
- SKILL.md
- references/gradle.md
- references/ide.md
- references/report.md
- scripts/run_tests_in_ide.kts
Open the folder on GitHubat commit bf19b3c
Compare with similar skills
Run Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Run Tests this skillAmplicode/spring-skills | 126 | — | ~432 | Automated safety check: Pass | None | |
| Grails Test Fixerapache/grails-core | 2.9k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Test Writing WorkflowiOfficeAI/AionUi | 33k | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Megatron Core Testing GuideNVIDIA/Megatron-LM | 18k | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| OpenROAD Module Test AdderThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~1.8k | Automated safety check: Pass | BSD-3-Clause | |
| New Event Sourceaws/aws-lambda-dotnet | 1.7k | — | ~3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Test Writing Workflow
iOfficeAI/AionUi
Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.
- Official
Megatron Core Testing Guide
NVIDIA/Megatron-LM
Guide to the Megatron-LM test system: layout, recipe YAML, running and adding unit and functional tests, golden values, marker filters and CI parity.
OpenROAD Module Test Adder
The-OpenROAD-Project/OpenROAD
Adds integration or unit tests to an OpenROAD module: writes the Tcl test, generates golden files and registers it in both CMake and Bazel.
- Official
New Event Source
aws/aws-lambda-dotnet
Add a new AWS event source attribute (e.g., Kinesis, Kafka, MQ) to the Lambda .NET Annotations framework, including the attribute class, source generator integration, CloudFormation writer, unit…
Aspire Integration Testing
DevBetterCom/DevBetterWeb
Write integration tests using .NET Aspire's testing facilities with xUnit.
More from Amplicode/spring-skills
All 16 skills in this repoMutation Testing
Amplicode/spring-skills
Set up and run mutation testing with PIT (pitest) on a Gradle project, and read the mutation score.
Amplicode Install
Amplicode/spring-skills
Installs the Amplicode IntelliJ plugin into IntelliJ IDEA (Ultimate/Community) and GigaIDE on the user's machine.
Coverage
Amplicode/spring-skills
Measure a project's code coverage and report the coverage number.
Spring Data Jdbc
Amplicode/spring-skills
Rules and guidelines for working with Spring Data JDBC in the project.
Spring Data Jpa
Amplicode/spring-skills
Rules and guidelines for working with Spring Data JPA in the project.
Spring Explore
Amplicode/spring-skills
Explores a Spring Boot application and builds primary context: tech stack, module structure, domain entities, REST endpoints.
Related
Works with
Categories
Questions about Run Tests
What does Run Tests do?
Run a Gradle project's tests by test type or module — unit, integration, or all. Run Tests is an agent skill from Amplicode/spring-skills. Run a Gradle project's tests by test type or module — unit, integration, or all.
When should I use Run Tests?
Run Tests fits situations like: the user wants to run; check the projects tests (e.g.
How do I install Run Tests in Claude Code?
Run `npx skills add Amplicode/spring-skills --skill run-tests -a claude-code`. Or copy the skill folder (skills/run-tests in Amplicode/spring-skills) into .claude/skills/run-tests in your project. Claude Code loads it when a task matches its description.
How do I install Run Tests in Codex?
Run `npx skills add Amplicode/spring-skills --skill run-tests -a codex`. Or copy the skill folder (skills/run-tests in Amplicode/spring-skills) into .agents/skills/run-tests in your project. Codex loads it when a task matches its description.
Can I use Run Tests in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Amplicode/spring-skills --skill run-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-tests, .gemini/skills/run-tests, .github/skills/run-tests and .opencode/skills/run-tests in your project.
What does Run Tests need to run?
SKILL.md names no scripts, command-line tools or credentials: Run Tests is instructions for the agent only. Our summary lists: Docker.
Does Run Tests access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Run Tests safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Run Tests use?
No licence was found for Run Tests or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Run Tests use?
About 432 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to Run Tests?
Skills that share tags, products or a category with Run Tests: Grails Test Fixer (apache/grails-core, 2.9k stars), Test Writing Workflow (iOfficeAI/AionUi, 33k stars), Megatron Core Testing Guide (NVIDIA/Megatron-LM, 18k stars) and OpenROAD Module Test Adder (The-OpenROAD-Project/OpenROAD, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Run Tests?
Amplicode (a GitHub organization) maintains it in Amplicode/spring-skills, which has 126 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 6, 2026.
Source: Amplicode/spring-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.