Move perf-review skill to .agents/skills to match repo convention

[dougqh]

What Does This Do

Fixes problem with skill visibility - now under generic agents dir rather than claude specific dir
Symlink-ed under old path for claude

Motivation

Work with both Codex & Claude

Additional Notes

From Claude...

Follow-up to #11912. The perf-review skill landed as real files under .claude/skills/perf-review, but the repo convention is: skills live canonically under .agents/skills/<name>, with .claude/skills/<name> a symlink into them so Claude Code still discovers them. The other five skills (apm-integrations, techdebt, migrate-groovy-to-java, migrate-junit-source-to-tabletest, review-groovy-migration) are all set up this way — perf-review was the outlier.

Change

• Move .claude/skills/perf-review/ → .agents/skills/perf-review/ (pure move, no content change).
• Add the compatibility symlink .claude/skills/perf-review → ../../.agents/skills/perf-review, matching the other skills (so Claude Code keeps finding it).
• Point the AGENTS.md reference at the canonical .agents/skills/perf-review/SKILL.md path.

Addresses the review comment on the merged #11912 ("looks like this landed in the wrong directory").

tag: ai generated
tag: no release note

🤖 Generated with Claude Code

[datadog-official]

More details

Pure file-move + symlink PR — files renamed from .claude/skills/perf-review/ to .agents/skills/perf-review/, symlink added matching the exact pattern of all five other skills, and AGENTS.md updated to the canonical path. All five skill files confirm readable via both canonical and symlink paths.

Was this helpful? React 👍 or 👎

_{📊 Validated against 5 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 416ffdd · What is Autotest? · Any feedback? Reach out in #autotest}

[datadog-official]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 57.17% (-0.01%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 416ffdd | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.05 s	13.91 s	[+0.3%; +1.7%] (maybe worse)
startup:insecure-bank:tracing:Agent	12.89 s	13.11 s	[-2.5%; -0.9%] (maybe better)
startup:petclinic:appsec:Agent	16.45 s	16.28 s	[-5.0%; +7.0%] (unstable)
startup:petclinic:iast:Agent	16.85 s	16.89 s	[-1.2%; +0.8%] (no difference)
startup:petclinic:profiling:Agent	16.26 s	16.84 s	[-7.7%; +0.8%] (no difference)
startup:petclinic:sca:Agent	16.81 s	16.55 s	[+0.4%; +2.8%] (maybe worse)
startup:petclinic:tracing:Agent	15.61 s	16.06 s	[-7.0%; +1.2%] (no difference)

Commit: 416ffdd0 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-14 23:17:32 UTC ℹ️ Start processing command /merge

---

2026-07-14 23:17:37 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-07-15 00:35:52 UTC ℹ️ MergeQueue: This merge request was merged