Official agent skill

Review Groovy Migration

Post-migration quality review. An agent skill from DataDog/dd-trace-java.

OfficialApache-2.0Auto-check passed

Install Review Groovy Migration

skills CLI

$ npx skills add DataDog/dd-trace-java --skill review-groovy-migration -a claude-code

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

GitHub CLI

$ gh skill install DataDog/dd-trace-java review-groovy-migration --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/DataDog/dd-trace-java.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-groovy-migration .claude/skills/review-groovy-migration && 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/

Paste into Claude Code

Install the "review-groovy-migration" agent skill from https://github.com/DataDog/dd-trace-java/tree/master/.agents/skills/review-groovy-migration into .claude/skills/review-groovy-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-groovy-migration", 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

$skill-installer install https://github.com/DataDog/dd-trace-java/tree/master/.agents/skills/review-groovy-migration

Type 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.

skills CLI

$ npx skills add DataDog/dd-trace-java --skill review-groovy-migration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install DataDog/dd-trace-java review-groovy-migration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-java.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/review-groovy-migration .agents/skills/review-groovy-migration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "review-groovy-migration" agent skill from https://github.com/DataDog/dd-trace-java/tree/master/.agents/skills/review-groovy-migration into .agents/skills/review-groovy-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-groovy-migration", 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.

skills CLI

$ npx skills add DataDog/dd-trace-java --skill review-groovy-migration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install DataDog/dd-trace-java review-groovy-migration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-java.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/review-groovy-migration .cursor/skills/review-groovy-migration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "review-groovy-migration" agent skill from https://github.com/DataDog/dd-trace-java/tree/master/.agents/skills/review-groovy-migration into .cursor/skills/review-groovy-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-groovy-migration", 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

$ gemini skills install https://github.com/DataDog/dd-trace-java.git --path .agents/skills/review-groovy-migration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add DataDog/dd-trace-java --skill review-groovy-migration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install DataDog/dd-trace-java review-groovy-migration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-java.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/review-groovy-migration .gemini/skills/review-groovy-migration && rm -rf skills-src

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

Paste into Gemini CLI

Install the "review-groovy-migration" agent skill from https://github.com/DataDog/dd-trace-java/tree/master/.agents/skills/review-groovy-migration into .gemini/skills/review-groovy-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-groovy-migration", 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.

GitHub CLI

$ gh skill install DataDog/dd-trace-java review-groovy-migration

Installs 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).

skills CLI

$ npx skills add DataDog/dd-trace-java --skill review-groovy-migration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-java.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/review-groovy-migration .github/skills/review-groovy-migration && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "review-groovy-migration" agent skill from https://github.com/DataDog/dd-trace-java/tree/master/.agents/skills/review-groovy-migration into .github/skills/review-groovy-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-groovy-migration", 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.

skills CLI

$ npx skills add DataDog/dd-trace-java --skill review-groovy-migration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install DataDog/dd-trace-java review-groovy-migration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/dd-trace-java.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/review-groovy-migration .opencode/skills/review-groovy-migration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "review-groovy-migration" agent skill from https://github.com/DataDog/dd-trace-java/tree/master/.agents/skills/review-groovy-migration into .opencode/skills/review-groovy-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-groovy-migration", 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: review-groovy-migration
GitHub stars: 736
Token cost: ~1.1k tokens
SKILL.md length: 255 words
Files: 1
Skills in repo: 9
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Post-migration quality review. An agent skill from DataDog/dd-trace-java.

Works in 6 steps: Load rules → Identify target files → Run grep-based detection → …
SKILL.md covers Step 1 — Load rules, Step 2 — Identify target files, Step 3 — Run grep-based… and Step 4 — Structural detection…, plus 2 more sections
Calls git

What it does

Review Groovy Migration is an agent skill from DataDog/dd-trace-java, published by the product's own GitHub organization. Post-migration quality review. Checks Java test files produced by migrate-groovy-to-java against the shared quality rules. Use after migration, or on any branch with recently migrated .java test files. Produces structured FINDING blocks grouped by severity, then offers to auto-fix BLOCKERs and WARNINGs.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Java and Datadog. The repository describes itself as: Datadog APM client for Java. The licence is Apache-2.0.

Example prompts

“/review-groovy-migration”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Load rules
Identify target files
Run grep-based detection
Structural detection (LLM-based)
Emit structured findings
Offer to fix

What it can do on your machine

Read from SKILL.md and the folder at commit c0cf602. 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
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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

Review Groovy Migration loads about 1.1k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 255 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~82
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 DataDog/dd-trace-java at commit c0cf602, republished under its Apache-2.0 licence (© DataDog). 255 words, ~1,075 tokens.

Download SKILL.mdSave it as .claude/skills/review-groovy-migration/SKILL.md (or your agent's skills folder).

name: review-groovy-migration
description: Post-migration quality review. Checks Java test files produced by migrate-groovy-to-java against the shared quality rules. Use after migration, or on any branch with recently migrated .java test files. Produces structured FINDING blocks grouped by severity, then offers to auto-fix BLOCKERs and WARNINGs.

Review migrated Java test files against the quality rules.

Step 1 — Load rules

Read .claude/skills/migrate-groovy-to-java/QUALITY_RULES.md in full before proceeding.

Step 2 — Identify target files

If the user specified files or a module path, use those. Otherwise, find files added on the current branch:

bash

MERGE_BASE=$(git merge-base HEAD origin/master 2>/dev/null || git merge-base HEAD master)
git diff "$MERGE_BASE" --name-only --diff-filter=A | grep 'src/test/java.*\.java$'

If no files are found, fall back to modified test files:

bash

git diff "$MERGE_BASE" --name-only | grep 'src/test/java.*\.java$'

Step 3 — Run grep-based detection

For each rule with a grep Detection pattern, run it over the target files. Use the patterns from the rules file. The patterns below assume GNU/ugrep-compatible regex (\b, \.); alternation uses grep -E "...|..." so it also works under BSD grep — adapt if your grep differs.

bash

# RULE-C01  (also fires on RULE-C02 lines — see dedup note below)
grep -rn "assertTrue(.*instanceof" <files>

# RULE-C02  (more specific than C01)
grep -rEn "assertTrue\(.*== *null.*instanceof|assertTrue\(.*instanceof.*== *null" <files>

# RULE-F01  (BLOCKER, but verify context — see note below)
# Run as three separate greps: word boundaries (\b) combined with | alternation
# misbehave under some grep builds, so do not merge these into one alternation.
grep -rEn "\bint\b.*[Ss]ampling[Pp]riority" <files>
grep -rEn "\bint\b.*\bpriority\b" <files>
grep -rEn "\bint\b.*\bmechanism\b" <files>

# RULE-A02
grep -rn '@WithConfig(key = "' <files>

# RULE-B01
grep -rn "new LinkedHashMap<>()" <files>

# RULE-C04
grep -rn "\.getTags()\.get(" <files>

# RULE-C05  (BLOCKER, but verify context — see note below)
# A matcher is only legitimate for genuinely non-deterministic values; otherwise it
# silently relaxes an assertion the Groovy original pinned. Cross-check the Groovy source.
grep -rEn "any\(\)|anyInt\(\)|anyLong\(\)|anyString\(\)|anyByte\(\)|anyBoolean\(\)|atLeastOnce\(\)" <files>

# RULE-D01
grep -rn "mock(.*Map.*\.class)" <files>

# RULE-G01
grep -rn "/\* [a-z]" <files>

# RULE-G02
grep -rEn "\(\) -> [a-zA-Z]+\.[a-zA-Z]+\(\)" <files>

# RULE-G05  (verify context — only when close() is the finally's sole statement and there
# is no surrounding logic requiring an explicit close; read the block before flagging)
grep -rEn "\} finally \{" <files>

# RULE-H01
grep -rEn "'18446744073709551[0-9]+'" <files>

# RULE-J02
grep -rEn "CarrierVisitor|forEachKeyValue" <files>

Read the full content of any file that has at least one hit, to understand the context.

Step 4 — Structural detection (LLM-based)

For rules without grep patterns (RULE-A01, RULE-B02, RULE-B03, RULE-C03, RULE-E01, RULE-E02, RULE-E03, RULE-G04, RULE-H02, RULE-I01, RULE-I02), read all target files and identify violations based on the Before/After examples in the rules.

Step 5 — Emit structured findings

For each issue found, emit one finding block:

FINDING
  file:     <absolute path>
  line:     <line number, or range start-end>
  rule:     <RULE-XNN>
  severity: <BLOCKER|WARNING|STYLE>
  excerpt:  <the offending code, single line>
  fix:      <the corrected code, single line or brief description>

Group all findings by severity: BLOCKERs first, then WARNINGs, then STYLEs.

At the end, print a one-line summary:

Summary: N blocker(s), M warning(s), K style issue(s) across F file(s).

If no issues are found:

No findings. All rules pass.

Step 6 — Offer to fix

After the summary, ask: "Fix all BLOCKERs and WARNINGs automatically? (yes / no / select rules)"

If the user agrees:

Apply each fix. For each file changed, run ./gradlew spotlessApply on its module after editing.
Re-run the grep checks to confirm the findings are resolved.
Report which findings were fixed and which (if any) require manual attention.

Files

Just SKILL.md in .agents/skills/review-groovy-migration of DataDog/dd-trace-java.

Open the folder on GitHubat commit c0cf602

Compare with similar skills

Review Groovy Migration 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.

Review Groovy Migration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Review Groovy Migration this skillDataDog/dd-trace-java	736	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Add Gc TestDataDog/jmxfetch	109	—	~1.1k	Automated safety check: Pass	Custom licence	2 mo ago
Brainstormingxpinjection/test-driven-spring-boot	112	52 repos	~2.6k	Automated safety check: Pass	MIT	1 mo ago
Code Design Rationale Investigatorcursor/plugins	11k	9 repos	~2.6k	Automated safety check: Pass	None	today
Android API Diffgkd-kit/gkd	43k	—	~796	Automated safety check: Pass	GPL-3.0	today
Video Cover Imageitwanger/toBeBetterJavaer	18k	—	~3.3k	Automated safety check: Pass	None	today

Similar skills

Add Gc Test
DataDog/jmxfetch
Official
Add integration tests to TestGCMetrics.java for new GC collector support added to new-gc-default-jmx-metrics.yaml.
109 GitHub stars~1.1k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
Brainstorming
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
112 GitHub starsUsed in 52 repos~2.6k tokens
Agent WorkflowsAuto-check passed
Code Design Rationale Investigator
cursor/plugins
Official
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
11k GitHub starsUsed in 9 repos~2.6k tokens
DevelopmentAuto-check passed
Android API Diff
gkd-kit/gkd
Looks up Android framework Java and AIDL APIs across versions with the android-api-diff CLI: signatures, availability, source files and hidden-API access code.
43k GitHub stars~796 tokensUpdated today
MobileAuto-check passed
Video Cover Image
itwanger/toBeBetterJavaer
Generate matched 3:4, 16:9, and 4:3 short-video cover images from toBeBetterJavaer video scripts or AI/Java technical topics.
18k GitHub stars~3.3k tokensUpdated today
Media & CreativeAuto-check passed
Lancedb Update Lance Dependency
lancedb/lancedb
Update LanceDB to a specific Lance release or tag. An agent skill from lancedb/lancedb.
12k GitHub stars~1.1k tokensUpdated today
DatabasesAuto-check passed

Questions about Review Groovy Migration

What does Review Groovy Migration do?

Post-migration quality review. An agent skill from DataDog/dd-trace-java. Review Groovy Migration is an agent skill from DataDog/dd-trace-java, published by the product's own GitHub organization. Post-migration quality review.

How do I install Review Groovy Migration in Claude Code?

Run `npx skills add DataDog/dd-trace-java --skill review-groovy-migration -a claude-code`. Or copy the skill folder (.agents/skills/review-groovy-migration in DataDog/dd-trace-java) into .claude/skills/review-groovy-migration in your project. Claude Code loads it when a task matches its description.

How do I install Review Groovy Migration in Codex?

Run `npx skills add DataDog/dd-trace-java --skill review-groovy-migration -a codex`. Or copy the skill folder (.agents/skills/review-groovy-migration in DataDog/dd-trace-java) into .agents/skills/review-groovy-migration in your project. Codex loads it when a task matches its description.

Can I use Review Groovy Migration 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 DataDog/dd-trace-java --skill review-groovy-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-groovy-migration, .gemini/skills/review-groovy-migration, .github/skills/review-groovy-migration and .opencode/skills/review-groovy-migration in your project.

What does Review Groovy Migration need to run?

Going by SKILL.md and its folder, Review Groovy Migration needs the command-line tools its instructions call (git).

Does Review Groovy Migration access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review Groovy Migration 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 Review Groovy Migration use?

Review Groovy Migration 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 Review Groovy Migration use?

About 1.1k tokens (SKILL.md is roughly 4.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 Review Groovy Migration?

Skills that share tags, products or a category with Review Groovy Migration: Add Gc Test (DataDog/jmxfetch, 109 stars), Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), Code Design Rationale Investigator (cursor/plugins, 11k stars) and Android API Diff (gkd-kit/gkd, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Groovy Migration?

DataDog (a GitHub organization, an official publisher) maintains it in DataDog/dd-trace-java, which has 736 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 2026.

Source: DataDog/dd-trace-java on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Review Groovy Migration

Install Review Groovy Migration

Facts

At a glance

What it does

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Step 1 — Load rules

Step 2 — Identify target files

Step 3 — Run grep-based detection

Step 4 — Structural detection (LLM-based)

Step 5 — Emit structured findings

Step 6 — Offer to fix

Files

Compare with similar skills

Similar skills

Add Gc Test

Brainstorming

Code Design Rationale Investigator

Android API Diff

Video Cover Image

Lancedb Update Lance Dependency

More from DataDog/dd-trace-java

Apm Integrations

Perf Review

Resolve Muzzle CI

Fix Continuation Leakage

Techdebt

Clarify Java Comments

Questions about Review Groovy Migration

Install Review Groovy Migration

Facts

At a glance

What it does

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Step 1 — Load rules

Step 2 — Identify target files

Step 3 — Run grep-based detection

Step 4 — Structural detection (LLM-based)

Step 5 — Emit structured findings

Step 6 — Offer to fix

Files

Compare with similar skills

Similar skills

More from DataDog/dd-trace-java

Related

Questions about Review Groovy Migration