getsentry/sentry-java is a Java and Android software development kit for sending application errors, events, and diagnostic information to Sentry. It is used by developers working with Java, Android, Kotlin, and other JVM-based applications to monitor software behavior. The catalogue rules, skills, instructions, and setting support workflows around this SDK.
Borrowing it
Nothing to install: this file belongs to getsentry/sentry-java. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/getsentry/sentry-java/main/.claude/skills/create-java-pr/SKILL.mdgit clone --depth 1 https://github.com/getsentry/sentry-javaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/getsentry/sentry-java/create-java-pr)<a href="https://agentmods.dev/skills/getsentry/sentry-java/create-java-pr"><img src="https://agentmods.dev/badge/skills/getsentry/sentry-java/create-java-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/getsentry/sentry-java/create-java-pr"><img src="https://agentmods.dev/badge/skills/getsentry/sentry-java/create-java-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00073 | $0.02289 |
| Opus 5.5 | $0.00029 | $0.00916 |
| Sonnet 5.5 | $0.00015 | $0.00458 |
| Haiku 4.5 | $0.00007 | $0.00229 |
Grade A, and why
create-java-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request (sentry-java)
Prepare local changes and create a pull request for the sentry-java repo.
For stacked PRs: read references/stacked-prs.md before proceeding. It is the source of truth for
stack structure, title naming, stack list format, and merge strategy.
Step 0: Determine PR Type From Git Branch Context
Infer PR type from the current branch before asking the user.
- Get current branch:
git branch --show-current
- Apply these rules:
- If branch is
mainormaster: default to a standalone PR.- Do not assume stack mode from
main. - Only use stack mode if the user explicitly asks for a stacked PR.
- Do not assume stack mode from
- If branch is not
main/master:- Check whether that branch already has a PR and what its base is:
gh pr list --head "$(git branch --show-current)" --json number,baseRefName,title --jq '.[0]' - If that branch PR exists and
baseRefNameis notmain/master, treat the work as a stacked PR context. - If that branch PR exists and
baseRefNameismain/master, also check whether other PRs target the current branch:gh pr list --base "$(git branch --show-current)" --json number,headRefName,title- If there are downstream PRs, treat this as next PR in an existing stack with the current branch as the stack base (collection branch).
- If there are no downstream PRs, treat it as standalone PR context.
- If no PR exists for the current branch, check whether other PRs target it:
gh pr list --base "$(git branch --show-current)" --json number,headRefName,title- If there are downstream PRs, treat this as next PR in an existing stack with the current branch as the stack base (collection branch).
- If there are no downstream PRs either, treat it as standalone PR context (fresh feature branch).
- Check whether that branch already has a PR and what its base is:
- If signals are mixed or ambiguous, ask one focused question to confirm.
PR types:
- Standalone PR — regular PR targeting
main. - First PR of a new stack — create collection branch from
main, then first PR off it. - Next PR in an existing stack — target the current stack base branch (usually the previous stack PR branch, or the collection branch if creating the first follow-up PR from the collection branch).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 218 lines · 73 tokens per session scan A 90bd9ad42639
create-java-pr is a skill published in the GitHub repository getsentry/sentry-java (1,357 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 2,289 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
engineer-bot-getting-started
An onboarding guide for an engineering delivery assistant. It helps define a repository, the allowed level of access, and the work needed before reviewing a code change.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
deliver-spec
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.
plugin-code-review-orchestrated
Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.
review-scope-resolver
Normalizes a PR, diff, commit, branch, file list, directory, module, class, or function into an exact review target with semantic clusters and routing signals for domain reviewer subskills. Use as the first pass of an orchestrated code review, when asked to resolve review scope, or when a raw review reference must be…
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.