Resolve Muzzle CI
DataDog/dd-trace-java
Diagnose and resolve dd-trace-java CI failures from a module's muzzle task or the runMuzzle aggregate.
Run tests headless and return only failing test output. An agent skill from jvm-skills/jvm-skills.
Install Test Gradle
$ npx skills add jvm-skills/jvm-skills --skill test-gradle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jvm-skills/jvm-skills test-gradle --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/jvm-skills/jvm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.junie/skills/test-gradle .claude/skills/test-gradle && 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 "test-gradle" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/test-gradle into .claude/skills/test-gradle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-gradle", 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/jvm-skills/jvm-skills/tree/main/.junie/skills/test-gradleType 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 jvm-skills/jvm-skills --skill test-gradle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jvm-skills/jvm-skills test-gradle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.junie/skills/test-gradle .agents/skills/test-gradle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-gradle" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/test-gradle into .agents/skills/test-gradle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-gradle", 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 jvm-skills/jvm-skills --skill test-gradle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jvm-skills/jvm-skills test-gradle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.junie/skills/test-gradle .cursor/skills/test-gradle && 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 "test-gradle" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/test-gradle into .cursor/skills/test-gradle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-gradle", 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/jvm-skills/jvm-skills.git --path .junie/skills/test-gradle--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 jvm-skills/jvm-skills --skill test-gradle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jvm-skills/jvm-skills test-gradle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.junie/skills/test-gradle .gemini/skills/test-gradle && 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 "test-gradle" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/test-gradle into .gemini/skills/test-gradle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-gradle", 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 jvm-skills/jvm-skills test-gradleInstalls 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 jvm-skills/jvm-skills --skill test-gradle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.junie/skills/test-gradle .github/skills/test-gradle && 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 "test-gradle" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/test-gradle into .github/skills/test-gradle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-gradle", 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 jvm-skills/jvm-skills --skill test-gradle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jvm-skills/jvm-skills test-gradle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.junie/skills/test-gradle .opencode/skills/test-gradle && 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 "test-gradle" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/test-gradle into .opencode/skills/test-gradle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-gradle", 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
test-gradle- GitHub stars
- 139
- Token cost
- ~314 tokens
- SKILL.md length
- 131 words
- Files
- 3
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Run tests headless and return only failing test output. An agent skill from jvm-skills/jvm-skills.
- Works in 2 steps: Run the test script (Bash tool, timeout… → Report the output as-is
- Tasks that involve Failing and flaky tests
- SKILL.md covers Argument handling and Instructions
- Runs Shell scripts from its folder
What it does
Test Gradle is an agent skill from jvm-skills/jvm-skills. Run tests headless and return only failing test output. Accepts optional test filter patterns like gradle (e.g. /test RankingGameTest)
Its SKILL.md is about 310 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `INSTALL.md` and `templates/run-tests.sh`).
It sits in Testing & QA, covering Failing and flaky tests. It works with Gradle. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Failing and flaky tests
Example prompts
- “/test-gradle”
Requirements
- A Bash shell
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Run the test script (Bash tool, timeout 600000)
- Report the output as-is
What it can do on your machine
Read from SKILL.md and the folder at commit c6d477f. 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 script files (Shell), 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
Test Gradle loads about 314 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 131 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from jvm-skills/jvm-skills at commit c6d477f, republished under its Apache-2.0 licence (© jvm-skills). 131 words, ~314 tokens.
Download SKILL.mdSave it as
.claude/skills/test-gradle/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- test-gradle
- description
- Run tests headless and return only failing test output. Accepts optional test filter patterns like gradle (e.g. /test *RankingGameTest)
- context
- fork
Run Tests Skill
Run tests and report results. Does NOT fix failures — fix them inline in the calling context.
Argument handling
CRITICAL: Only add --tests flags if the user explicitly passed filter patterns. /test with NO arguments MUST run ALL tests — do NOT infer filters from branch name, recent changes, or context.
Examples:
/test→./scripts/run-tests.sh(ALL tests, no filters)/test *RankingGameSetupTest→./scripts/run-tests.sh --tests "*RankingGameSetupTest"/test *SetupTest *LobbyTest→./scripts/run-tests.sh --tests "*SetupTest" --tests "*LobbyTest"
If the argument already contains --tests, pass it through as-is.
Instructions
Run the test script (Bash tool, timeout 600000):
bash ./scripts/run-tests.sh [--tests "pattern"]...Report the output as-is:
- If output says "All tests passed." → report success, done.
- If output shows "## Failed Tests" → report the failures verbatim. Do NOT fix them. Do NOT launch subagents. Return the raw failure output to the caller.
© jvm-skills, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in .junie/skills/test-gradle of jvm-skills/jvm-skills.
- SKILL.md
- INSTALL.md
- templates/run-tests.sh
Open the folder on GitHubat commit c6d477f
Compare with similar skills
Test Gradle 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 |
|---|---|---|---|---|---|---|
| Test Gradle this skilljvm-skills/jvm-skills | 139 | — | ~314 | Automated safety check: Pass | Apache-2.0 | |
| Resolve Muzzle CIDataDog/dd-trace-java | 736 | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Grails Test Fixerapache/grails-core | 2.9k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Stewardyschimke/compose-ai-tools | 117 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Pester Failure AnalysisPowerShell/PowerShell | 56k | — | ~5.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
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.
- Official
Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Steward
yschimke/compose-ai-tools
Drive a pull request on this repository to green — which fast checks to run before pushing, how to read a red check, and what to do about a review comment.
Pester Failure Analysis
PowerShell/PowerShell
Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
More from jvm-skills/jvm-skills
All 16 skills in this repoMutation Testing
jvm-skills/jvm-skills
Bootstrap pitest via the info.solidsoft.pitest Gradle plugin with Kotlin-sane defaults, run mutation tests scoped to changed classes, interpret surviving mutants from mutations.xml, triage…
Ralph Coverage
jvm-skills/jvm-skills
Run Ralph in coverage mode — iteratively write tests for untested classes until coverage targets are met.
Skill Scout
jvm-skills/jvm-skills
Run the skill-scout loop — scan the next batch of unscanned JVM-conference rosters for speaker-created AI skills and apply results to the CSV store via the overnight Workflow.
Spec
jvm-skills/jvm-skills
Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed.
UI Review
jvm-skills/jvm-skills
Verify UI/UX by running Playwright tests and reviewing screenshots.
Kotest
jvm-skills/jvm-skills
Write a new Kotlin test, or modernize an existing one, using Kotest matchers and idiomatic Kotlin test style — backticked names, apply/assertSoftly blocks, and existing object mothers and helpers.
Related
Works with
Categories
Questions about Test Gradle
What does Test Gradle do?
Run tests headless and return only failing test output. An agent skill from jvm-skills/jvm-skills. Test Gradle is an agent skill from jvm-skills/jvm-skills. Run tests headless and return only failing test output.
When should I use Test Gradle?
Test Gradle fits situations like: tasks that involve Failing and flaky tests.
How do I install Test Gradle in Claude Code?
Run `npx skills add jvm-skills/jvm-skills --skill test-gradle -a claude-code`. Or copy the skill folder (.junie/skills/test-gradle in jvm-skills/jvm-skills) into .claude/skills/test-gradle in your project. Claude Code loads it when a task matches its description.
How do I install Test Gradle in Codex?
Run `npx skills add jvm-skills/jvm-skills --skill test-gradle -a codex`. Or copy the skill folder (.junie/skills/test-gradle in jvm-skills/jvm-skills) into .agents/skills/test-gradle in your project. Codex loads it when a task matches its description.
Can I use Test Gradle 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 jvm-skills/jvm-skills --skill test-gradle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-gradle, .gemini/skills/test-gradle, .github/skills/test-gradle and .opencode/skills/test-gradle in your project.
What does Test Gradle need to run?
Going by SKILL.md and its folder, Test Gradle needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Test Gradle 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 Test Gradle 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. Review the folder before installing.
What licence does Test Gradle use?
Test Gradle is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Test Gradle use?
About 314 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Test Gradle?
Skills that share tags, products or a category with Test Gradle: Resolve Muzzle CI (DataDog/dd-trace-java, 736 stars), Grails Test Fixer (apache/grails-core, 2.9k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars) and Steward (yschimke/compose-ai-tools, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Gradle?
jvm-skills (a GitHub organization) maintains it in jvm-skills/jvm-skills, which has 139 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on August 31, 2026.
Source: jvm-skills/jvm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.