Agent skill

Grails Test Fixer

by apache in 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.

Apache-2.0Auto-check passedTesting & QA

Install Grails Test Fixer

skills CLI
$ npx skills add apache/grails-core --skill test-fixer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install apache/grails-core test-fixer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/apache/grails-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/test-fixer .claude/skills/test-fixer && rm -rf skills-src

Use ~/.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/

Facts

Skill name
test-fixer
GitHub stars
2.9k
Token cost
~1.1k tokens
SKILL.md length
369 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guides running, reviewing and fixing test failures across grails-core modules with Gradle, including targeted runs and the aggregate HTML and Markdown reports.

  • Running a single failing spec or module in grails-core
  • SKILL.md covers What I Do, When to Use Me, Key Tasks and Aggregate Test Reports, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Verifying affected module tests before a commit

What it does

The skill helps the agent run tests in grails-core efficiently. Targeted runs use a Gradle module path with a --tests filter to save time, full runs use ./gradlew test --continue so later modules still run after an earlier failure, and a single module can be run by its own task path. It names the unit source set under src/test/groovy and the integration source set under src/integration-test/groovy.

Aggregation lives in the grails-test-report project: running its check task with --continue produces unit, integration and combined reports in both HTML and Markdown under grails-test-report/build/reports/tests. Reports summarize whatever XML results exist on disk, so a full run without --continue can be partial, and stale results are cleared by running clean first. The skill also helps triage failing specs, static state pollution and regressions after a dependency upgrade or refactor.

When your agent uses it

  • Running a single failing spec or module in grails-core
  • Verifying affected module tests before a commit
  • Triaging regressions after a dependency upgrade or refactor
  • Reading the aggregate test report from grails-test-report

Example prompts

  • “Run only the BasicCollection tests in the hibernate7 core module and tell me what fails.”
  • “Run the full suite with --continue and summarize the combined Markdown report.”
  • “Find out whether this spec failure comes from static state left behind by another test.”

Requirements

  • A grails-core checkout with the Gradle wrapper

What it can do on your machine

Read from SKILL.md and the folder at commit 3d6db18. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    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

Grails Test Fixer loads about 1.1k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 369 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 apache/grails-core at commit 3d6db18, republished under its Apache-2.0 licence (© apache). 369 words, ~1,128 tokens.

Download SKILL.mdSave it as .claude/skills/test-fixer/SKILL.md (or your agent's skills folder).
name
test-fixer
description
Guide for running, reviewing, and fixing test failures across grails-core modules using Gradle test reports
license
Apache-2.0
<!--
SPDX-License-Identifier: Apache-2.0

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements; and to You under the Apache License, Version 2.0.
-->

What I Do

  • Guide targeted and full test runs across grails-core modules.
  • Help interpret Gradle HTML and XML test reports.
  • Help triage failing specs, static state pollution, and module-specific regressions.

When to Use Me

Activate this skill when:

  • Running a failing module or specific spec.
  • Preparing a commit and verifying affected module tests.
  • Triaging regressions after a dependency upgrade or refactor.
  • Reviewing aggregate test results from :grails-test-report.

Key Tasks

To save time, run only related tests:

bash
./gradlew :grails-data-hibernate7-core:test --tests "grails.gorm.tests.BasicCollection*"
Full Run
bash
./gradlew test --continue

Use --continue when you need later modules to run after an earlier module fails.


Aggregate Test Reports

The grails-test-report project owns repository test aggregation.

bash
./gradlew :grails-test-report:check --continue

This generates:

  • Unit HTML: grails-test-report/build/reports/tests/test/index.html
  • Unit Markdown: grails-test-report/build/reports/tests/test.md
  • Integration HTML: grails-test-report/build/reports/tests/integrationTest/index.html
  • Integration Markdown: grails-test-report/build/reports/tests/integrationTest.md
  • Combined HTML: grails-test-report/build/reports/tests/combined/index.html
  • Combined Markdown: grails-test-report/build/reports/tests/combined.md

The aggregate report includes root subprojects that define matching test or integrationTest tasks.

The collected unit and integration Test tasks are finalized by their matching aggregate report tasks. Reports are attempted after failures and after targeted module test runs, but they summarize the XML results currently available on disk. Use --continue for full-suite runs so Gradle keeps scheduling later test tasks after an earlier failure; without it, reports can be partial. Run clean first when stale XML results should be excluded.


Running Tests for a Specific Module

bash
# All tests in a module
./gradlew :grails-data-hibernate7-dbmigration:test

# A specific spec
./gradlew :grails-data-hibernate7-dbmigration:test \
  --tests "org.grails.plugins.databasemigration.command.DbmGenerateGormChangelogCommandSpec"

# A specific feature method
./gradlew :grails-data-hibernate7-core:test \
  --tests "org.grails.orm.hibernate.FooSpec.my feature name"

# Force rerun even if Gradle thinks it is up-to-date
./gradlew :grails-data-hibernate7-core:test --rerun-tasks

Show full SKILL.md (157 more words)Show less

Test Source Layout

Source setDirectoryTask
Unit testssrc/test/groovy/test
Integration testssrc/integration-test/groovy/integrationTest

Most specs in grails-core are unit tests (src/test/groovy/) run by the test task. A small number of modules use integrationTest for full Spring context tests.


Parallel Test Execution

Tests run in parallel (maxParallelForks defaults to 4 on CI and to availableProcessors * 3/4 otherwise; override with -PmaxTestParallel). This can cause:

  • Static state pollution: one test mutating a static field that another test reads.
  • Port conflicts: multiple test JVMs binding the same port.
  • @Shared field contamination: shared state not properly cleaned up between feature methods.

To diagnose flaky failures, rerun with forced serial execution:

bash
./gradlew :module:test -PmaxTestParallel=1 --rerun-tasks

Test Configuration Flags

PropertyEffect
skipTestsSkips all Test tasks (build only)
maxTestParallel=NOverride parallel fork count
onlyFunctionalTestsRun only functional test suites
skipHibernate7TestsSkip H7-specific test suites
onlyMongodbTestsRun only MongoDB test suites
onlyCoreTestsRun only core module tests

XML Report Location

Gradle writes JUnit XML test results to:

text
<module>/build/test-results/
├── test/
│   └── TEST-org.grails.SomeSpec.xml
└── integrationTest/
    └── TEST-org.grails.SomeIntegrationSpec.xml

© apache, 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

Just SKILL.md in .agents/skills/test-fixer of apache/grails-core.

Open the folder on GitHubat commit 3d6db18

Compare with similar skills

Grails Test Fixer 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.

Grails Test Fixer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Grails Test Fixer this skillapache/grails-core2.9k—~1.1kAutomated safety check: PassApache-2.0
Designing TestsCloudAI-X/claude-workflow-v21.4k1 repos~1.5kAutomated safety check: PassMIT
Temporal Python Testingwshobson/agents40k11 repos~1.2kAutomated safety check: PassMIT
Testingredis/RedisInsight8.9k—~3.3kAutomated safety check: PassCustom licence
Run Testsrunceel/ReactiveProperty944—~3.6kAutomated safety check: PassMIT
Flutter TestingMADTeacher/mad-agents-skills110—~1.5kAutomated safety check: PassMIT

Similar skills

  • Designing Tests

    CloudAI-X/claude-workflow-v2

    Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub starsUsed in 1 repo~1.5k tokens
    Testing & QAAuto-check passed
  • Test Temporal workflows with pytest, time-skipping, and mocking strategies.

    40k GitHub starsUsed in 11 repos~1.2k tokens
    Testing & QAAuto-check passed
  • Testing

    redis/RedisInsight

    Official

    Unit/integration testing standards for RedisInsight using Jest and Testing Library: test structure, the renderComponent helper, faker for test data, mocking patterns, and waitFor instead of fixed…

    8.9k GitHub stars~3.3k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Run Tests

    runceel/ReactiveProperty

    Runs .NET tests with dotnet test. An agent skill from runceel/ReactiveProperty.

    944 GitHub stars~3.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Flutter Testing

    MADTeacher/mad-agents-skills

    Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins.

    110 GitHub stars~1.5k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Frappe Testing Unit

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests.

    187 GitHub stars~3k tokensUpdated 20 days ago
    Testing & QAAuto-check passed

More from apache/grails-core

All 9 skills in this repo
  • Grails Developer Guide

    apache/grails-core

    Guides building Grails web applications and REST APIs with GORM, controllers, services, views, plugins and Spock and Geb testing.

    2.9k GitHub stars~4.9k tokensUpdated today
    Auto-check passed
  • Groovy 5 Developer Guide

    apache/grails-core

    Guidance for Groovy 5 work in Grails projects: syntax, closures, traits, DSLs, metaprogramming, Spock tests, static compilation and Java 21 integration.

    2.9k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Guides changes to the grails-data-hibernate7 module, covering domain binding, Hibernate 5 to 7 migration work, generators and integration specs.

    2.9k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Guide for writing modern Java 21 in a Grails and Groovy codebase: records, sealed classes, pattern matching, text blocks and how Java works alongside Groovy.

    2.9k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Grails Violation Fixer

    apache/grails-core

    Guide to running, reading and fixing code style and analysis violations in grails-core with CodeNarc, Checkstyle, PMD, SpotBugs, Spotless and JaCoCo through Gradle.

    2.9k GitHub stars~3.9k tokensUpdated today
    Auto-check passed
  • Grails Gradle Developer

    apache/grails-core

    Guides Gradle 9 build changes in apache/grails-core on the 8.0.x line, favoring the repo's convention plugins, BOM platforms and patterns over generic Gradle advice.

    2.9k GitHub stars~11k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Grails Test Fixer

What does Grails Test Fixer do?

Guides running, reviewing and fixing test failures across grails-core modules with Gradle, including targeted runs and the aggregate HTML and Markdown reports. The skill helps the agent run tests in grails-core efficiently./gradlew test --continue so later modules still run after an earlier failure, and a single module can be run by its own task path.

When should I use Grails Test Fixer?

Grails Test Fixer fits situations like: running a single failing spec or module in grails-core; verifying affected module tests before a commit; triaging regressions after a dependency upgrade or refactor; reading the aggregate test report from grails-test-report.

How do I install Grails Test Fixer in Claude Code?

Run `npx skills add apache/grails-core --skill test-fixer -a claude-code`. Or copy the skill folder (.agents/skills/test-fixer in apache/grails-core) into .claude/skills/test-fixer in your project. Claude Code loads it when a task matches its description.

How do I install Grails Test Fixer in Codex?

Run `npx skills add apache/grails-core --skill test-fixer -a codex`. Or copy the skill folder (.agents/skills/test-fixer in apache/grails-core) into .agents/skills/test-fixer in your project. Codex loads it when a task matches its description.

Can I use Grails Test Fixer 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 apache/grails-core --skill test-fixer -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-fixer, .gemini/skills/test-fixer, .github/skills/test-fixer and .opencode/skills/test-fixer in your project.

What does Grails Test Fixer need to run?

SKILL.md names no scripts, command-line tools or credentials: Grails Test Fixer is instructions for the agent only. Our summary lists: A grails-core checkout with the Gradle wrapper.

Does Grails Test Fixer 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 Grails Test Fixer 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 Grails Test Fixer use?

Grails Test Fixer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Grails Test Fixer use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Grails Test Fixer?

Skills that share tags, products or a category with Grails Test Fixer: Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars), Temporal Python Testing (wshobson/agents, 40k stars), Testing (redis/RedisInsight, 8.9k stars) and Run Tests (runceel/ReactiveProperty, 944 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grails Test Fixer?

apache (a GitHub organization) maintains it in apache/grails-core, which has 2,934 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

Source: apache/grails-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.