一键在 Manus 中运行任何 Skill

164-java-profiling-verify

星标0

分支2

更新时间2026年3月19日 20:26

Use when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation. Part of the skills-for-java project

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

jabrena

jabrena/cursor-rules-examples

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Java Profiling Workflow / Step 4 / Verify results

Verify performance optimizations through rigorous before/after comparison: ensure baseline and post-refactoring profiling data use identical test conditions, generate post-refactoring reports, compare metrics (memory, CPU, GC, threading), perform side-by-side flamegraph analysis, document findings in profiling-comparison-analysis-YYYYMMDD.md and profiling-final-results-YYYYMMDD.md, and validate success criteria.

What is covered in this Skill?

Pre-refactoring baseline: run profiler with same load before changes
Post-refactoring: generate new reports with identical test conditions
Comparison: memory (leaks, allocations, GC), CPU (hotspots, contention), visual flamegraph comparison
Documentation: profiler/docs/profiling-comparison-analysis-YYYYMMDD.md, profiler/docs/profiling-final-results-YYYYMMDD.md
File naming: baseline/after suffixes, timestamp-based organization
Validation: verify reports exist, compare metrics, identify regressions

Scope: Identical test conditions are critical. Document test scenarios. Validate application runs with refactored code before generating new reports.

Constraints

Use identical test conditions between baseline and post-refactoring. Verify both report sets are complete. Document test scenarios.

CONSISTENCY: Use identical test conditions and load patterns for baseline and post-refactoring
VALIDATE: Ensure both baseline and post-refactoring reports exist and are non-empty before comparison
DOCUMENT: Record test scenarios and load patterns for reproduction
BEFORE APPLYING: Read the reference for comparison templates and validation steps

When to use this skill

Verify performance fix
Performance benchmark

Reference

For detailed guidance, examples, and constraints, see references/164-java-profiling-verify.md.

同仓库更多 Skills

同仓库

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	164-java-profiling-verify
description	Use when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation. 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 4 / Verify results

What is covered in this Skill?

Pre-refactoring baseline: run profiler with same load before changes
Post-refactoring: generate new reports with identical test conditions
Comparison: memory (leaks, allocations, GC), CPU (hotspots, contention), visual flamegraph comparison
Documentation: profiler/docs/profiling-comparison-analysis-YYYYMMDD.md, profiler/docs/profiling-final-results-YYYYMMDD.md
File naming: baseline/after suffixes, timestamp-based organization
Validation: verify reports exist, compare metrics, identify regressions

Scope: Identical test conditions are critical. Document test scenarios. Validate application runs with refactored code before generating new reports.

Constraints

Use identical test conditions between baseline and post-refactoring. Verify both report sets are complete. Document test scenarios.

CONSISTENCY: Use identical test conditions and load patterns for baseline and post-refactoring
VALIDATE: Ensure both baseline and post-refactoring reports exist and are non-empty before comparison
DOCUMENT: Record test scenarios and load patterns for reproduction
BEFORE APPLYING: Read the reference for comparison templates and validation steps

When to use this skill

Verify performance fix
Performance benchmark

Reference

For detailed guidance, examples, and constraints, see references/164-java-profiling-verify.md.