Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

162-java-profiling-analyze

Estrelas0

Forks2

Atualizado19 de março de 2026 às 20:26

Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. Part of the skills-for-java project

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

jabrena

jabrena/cursor-rules-examples

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	162-java-profiling-analyze
description	Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. Part of the skills-for-java project
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

Java Profiling Workflow / Step 2 / Analyze profiling data

Analyze profiling results systematically: inventory results (flamegraphs, JFR, GC logs, thread dumps), identify problems (memory leaks, CPU hotspots, threading issues), document findings using standardized templates (profiling-problem-analysis-YYYYMMDD.md, profiling-solutions-YYYYMMDD.md), prioritize using Impact/Effort scores, and correlate multiple profiling files for validation.

What is covered in this Skill?

Inventory: scan profiler/results/ for allocation-flamegraph, heatmap-cpu, memory-leak, *.jfr, *.log, *.txt
Problem identification: memory (leaks, excessive allocations, GC pressure), performance (CPU hotspots, blocking), threading (deadlocks, contention, pool saturation)
Documentation: docs/profiling-problem-analysis-YYYYMMDD.md, docs/profiling-solutions-YYYYMMDD.md
Prioritization: Impact (1–5) / Effort (1–5), focus on high priority first
Tools: async-profiler, JFR, JProfiler/YourKit, GCViewer, flamegraphs, heatmaps

Scope: Validate profiling results represent realistic load scenarios. Cross-reference multiple files. Include quantitative metrics.

Constraints

Validate profiling results represent realistic load before analysis. Document assumptions and limitations. Cross-reference multiple files.

VALIDATE: Ensure profiling results represent realistic load scenarios before analysis
DOCUMENT: Record assumptions and limitations in analysis reports
CROSS-REFERENCE: Use multiple profiling files to validate findings
BEFORE APPLYING: Read the reference for problem analysis and solutions templates

When to use this skill

Analyze JFR profile
Profile analysis
Performance analysis

Reference

For detailed guidance, examples, and constraints, see references/162-java-profiling-analyze.md.

Mais deste repositório

mesmo repositório

014-agile-create-user-story

jabrena/cursor-rules-examples

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. Part of the skills-for-java project

2026-03-190

020-planning-enhance-ai-plan-mode

jabrena/cursor-rules-examples

Use when creating a plan using Plan model and enhancing structured design plans in Cursor Plan mode for Java implementations. Use when the user wants to create a plan, design an implementation, structure a development plan, or use plan mode for outside-in TDD, feature implementation, or refactoring work. Part of the skills-for-java project

2026-03-190

030-architecture-adr-general

jabrena/cursor-rules-examples

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. Part of the skills-for-java project

2026-03-190

031-architecture-adr-functional-requirements

jabrena/cursor-rules-examples

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. Part of the skills-for-java project

2026-03-190

032-architecture-adr-non-functional-requirements

jabrena/cursor-rules-examples

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. Part of the skills-for-java project

2026-03-190

033-architecture-diagrams

jabrena/cursor-rules-examples

Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, and ER (Entity Relationship) diagrams — through a modular, step-based interactive process that adapts to your specific visualization needs. Part of the skills-for-java project

2026-03-190

name	162-java-profiling-analyze
description	Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. Part of the skills-for-java project
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

Java Profiling Workflow / Step 2 / Analyze profiling data

What is covered in this Skill?

Inventory: scan profiler/results/ for allocation-flamegraph, heatmap-cpu, memory-leak, *.jfr, *.log, *.txt
Problem identification: memory (leaks, excessive allocations, GC pressure), performance (CPU hotspots, blocking), threading (deadlocks, contention, pool saturation)
Documentation: docs/profiling-problem-analysis-YYYYMMDD.md, docs/profiling-solutions-YYYYMMDD.md
Prioritization: Impact (1–5) / Effort (1–5), focus on high priority first
Tools: async-profiler, JFR, JProfiler/YourKit, GCViewer, flamegraphs, heatmaps

Scope: Validate profiling results represent realistic load scenarios. Cross-reference multiple files. Include quantitative metrics.

Constraints

Validate profiling results represent realistic load before analysis. Document assumptions and limitations. Cross-reference multiple files.

VALIDATE: Ensure profiling results represent realistic load scenarios before analysis
DOCUMENT: Record assumptions and limitations in analysis reports
CROSS-REFERENCE: Use multiple profiling files to validate findings
BEFORE APPLYING: Read the reference for problem analysis and solutions templates

When to use this skill

Analyze JFR profile
Profile analysis
Performance analysis

Reference

For detailed guidance, examples, and constraints, see references/162-java-profiling-analyze.md.