Add a /test skill to run singular tests or per module tests

[adinauer]

📜 Description

💡 Motivation and Context

💚 How did you test it?

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

• Add a /test skill to run singular tests or per module tests by adinauer in #5111

---

_{🤖 This preview updates automatically when you update the PR.}

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

### Features

- Add a /test skill to run singular tests or per module tests ([#5111](https://github.com/getsentry/sentry-java/pull/5111))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description or adding a skip-changelog label.

Generated by 🚫 dangerJS against 0fa5d7f

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Test task detection misses Android module naming pattern

Medium Severity

The module-to-test-task mapping only handles sentry-android-* and sentry-compose* as needing testDebugUnitTest, but sentry-launchdarkly-android is also an Android library module (it uses the com.android.library Gradle plugin) that requires testDebugUnitTest. Since its name doesn't match either pattern, it falls through to the plain test task, which would fail. The pattern matching needs to also account for non-sentry-android-*-prefixed Android modules.

 

[cursor]

Interactive mode tool not listed in allowed-tools

Medium Severity

The skill's interactive mode (Steps 0, 1, and 3a) instructs Claude to use AskUserQuestion at multiple decision points, but allowed-tools only lists Bash, Read, Glob. Since AskUserQuestion is a distinct Claude Code tool that can be included in allowed-tools, its omission means the interactive mode feature described throughout the skill cannot function as intended when tool restrictions are enforced.

Additional Locations (1)

• .claude/skills/test/SKILL.md#L13-L15