Skip to content
cccskills
FreePublished on GitHub

161-java-profiling-detect

Use when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven profiling (CPU, memory, threading, GC, I/O), interactive profiling scripts, JFR integration with Java 25 (JEP 518, JEP 520), or collecting profiling data with flamegraphs and JFR recordings. This should trigger for requests such as Improve the code with profiling; Apply Profiling; Refactor the code with profiling; Add profiling support; Collect JFR or async-profiler data for Java performance. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth
See how to install

Files included (4)

  • SKILL.md3.5 KB
  • references/161-java-profiling-detect.md8.3 KB
  • scripts/profile-java-process.sh60.3 KB
  • scripts/run-java-process-for-profiling.sh16.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Java Profiling Workflow / Step 1 / Collect data to measure potential issues

Set up the Java profiling detection phase using a trusted preinstalled async-profiler v4.x, problem-driven interactive profiling scripts, and comprehensive data collection for CPU hotspots, memory leaks, lock contention, GC issues, and I/O bottlenecks. Uses JEP 518 (Cooperative Sampling) and JEP 520 (Method Timing) for reduced overhead.

What is covered in this Skill?

  • Run application with profiling JVM flags (run-java-process-for-profiling.sh)
  • Interactive profiling script (profiler/scripts/profile-java-process.sh) — copy exact template
  • Directory structure: profiler/scripts/, profiler/results/, profiler/current/
  • Automated OS/architecture detection and trusted preinstalled async-profiler validation
  • CPU, memory, lock, GC, I/O profiling modes
  • Flamegraph and JFR output with timestamped results

Scope: Use the exact bash script templates without modification or interpretation.

Constraints

Copy bash scripts exactly from templates. Ensure JVM flags are applied for profiling compatibility. Verify Java processes are running before attaching profiler.

  • CRITICAL: Copy the bash script templates exactly — do not modify, interpret, or enhance
  • SETUP: Create profiler directory structure: profiler/scripts, profiler/results
  • SUPPLY CHAIN: Do not download profiler binaries at runtime; require ASYNC_PROFILER_HOME or profiler/current to point to a trusted, preinstalled async-profiler distribution
  • EXECUTABLE: Make scripts executable with chmod +x
  • BEFORE APPLYING: Read the reference for exact script templates and setup instructions
  • EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes
  • EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

When to use this skill

  • Improve the code with profiling
  • Apply Profiling
  • Refactor the code with profiling
  • Add profiling support
  • Collect JFR or async-profiler data for Java performance

Workflow

  1. Read profiling setup reference

Read references/161-java-profiling-detect.md and use script templates exactly as provided.

  1. Create profiler workspace and scripts

Create profiler/scripts and profiler/results, copy setup/profile scripts verbatim, and make scripts executable.

  1. Run application with profiling compatibility

Start Java process with required profiling JVM flags and verify target process availability for profiler attachment.

  1. Collect profiling artifacts

Capture CPU/memory/lock/GC/I/O data and produce timestamped flamegraph and JFR outputs for analysis.

Reference

For detailed guidance, examples, and constraints, see references/161-java-profiling-detect.md.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

001-commands-inventory

Free

Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 19, 2026

002-agents-inventory

Free

Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 19, 2026

003-skills-inventory

Free

Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 19, 2026

004-commands-installation

Free

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 19, 2026

005-agents-installation

Free

Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .github/agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Bootstrap .codex/agents; Copy robot agents. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 19, 2026

012-agile-epic

Free

Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 19, 2026

See all skills by jabrena

Report a problem with this skill