rrezartprebreza/spring-boot-skills / skills/spring-boot-4/jvm-diagnostics
jvm-diagnostics
VerifiedUse when diagnosing high CPU, memory growth, long GC pauses, deadlocks or thread starvation in a Spring Boot JVM. Choose bounded evidence collection and distinguish observations from hypotheses; not general observability setup.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.9 KB |
| agents/openai.yaml | config | 248 B |
| examples/bad-diagnosis.md | markdown | 190 B |
| examples/good-diagnosis.md | markdown | 627 B |
| references/collection.md | markdown | 1.7 KB |
references/collection.md
View on GitHub# Bounded collection
Before a live command, confirm the exact target and approved collection scope. Even thread
samples can pause work and contain sensitive names; do not equate filesystem read-only with
zero runtime impact. Production collection always requires explicit authorization.
- Start with existing redacted logs/metrics. Avoid VM.command_line, VM.system_properties,
process argument listings and environment dumps unless the sensitive data is required.
- Inspect `jcmd <pid> help <command>` for that JVM's syntax and documented impact.
- Repeated Thread.print samples can reveal progress and locks; collect a bounded count with
timestamps. Do not loop indefinitely or signal an unverified PID.
- A JFR recording requires an approved duration, settings, local output path and disk limit.
For an approved JDK 21 target, a possible command shape is
`jcmd <pid> JFR.start name=triage settings=default duration=60s maxsize=64m filename=<approved-local-file>`.
Verify supported options first. Do not stop an unrelated recording. Recordings can contain
sensitive data and maxsize does not eliminate every I/O or runtime cost.
- Histograms scan the heap at a safepoint. Some forms trigger full GC. Heap dumps can pause
the application and require substantial disk; obtain explicit approval, check free space,
restrict local access and state expected impact without promising a fixed pause duration.
- No collection/upload service, public Actuator dump endpoint or remote debugging listener
is needed. Do not upload artifacts. Agree retention and deletion with the evidence owner.
If attach tools are unavailable or denied, report the limitation. Do not install privileged
agents, change container permissions or restart the service to work around it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |