161-java-profiling-detect
This skill sets up Java application profiling using async-profiler v4.0 and JFR to detect performance bottlenecks in CPU, memory, threading, garbage collection, and I/O. Use it when requests ask to improve code with profiling, apply profiling, refactor with profiling, or add profiling support to identify and measure performance issues in Java applications.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/161-java-profiling-detect && cp -r /tmp/161-java-profiling-detect/skills/161-java-profiling-detect ~/.claude/skills/161-java-profiling-detectSKILL.md
# Java Profiling Workflow / Step 1 / Collect data to measure potential issues Set up the Java profiling detection phase: automated environment setup with async-profiler v4.0, 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 async-profiler download - 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 - **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 ## Workflow 1. **Read profiling setup reference** Read `references/161-java-profiling-detect.md` and use script templates exactly as provided. 2. **Create profiler workspace and scripts** Create `profiler/scripts` and `profiler/results`, copy setup/profile scripts verbatim, and make scripts executable. 3. **Run application with profiling compatibility** Start Java process with required profiling JVM flags and verify target process availability for profiler attachment. 4. **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](references/161-java-profiling-detect.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
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. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/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 .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
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 cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project