How do I install the 164 Java Profiling Verify skill?

Run npx skillmds add majiayu000/164-java-profiling-verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 164 Java Profiling Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 164 Java Profiling Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 164 Java Profiling Verify free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 164 Java Profiling Verify?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

164 Java Profiling Verify by majiayu000

Name: 164 Java Profiling Verify
Rating: 4.5 (4 reviews)
Author: majiayu000

164 Java Profiling Verify

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. This should trigger for requests such as Verify performance fix; Verify the performance; Verify the memory; Verify the threading. Part of cursor-rules-java project

majiayu000 795491d 2 files · 5.3 KB Updated Sep 9, 2026 567 repo stars

File contents

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
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

Verify performance fix
Verify the performance
Verify the memory
Verify the threading
Verify the GC
Verify the profiling
Verify the profiling
Performance benchmark

Workflow

Read verification reference and confirm baseline data

Read references/164-java-profiling-verify.md and verify baseline artifacts exist and are non-empty.

Generate post-refactoring profiling data

Run profiling with identical load/test conditions to produce comparable post-refactoring artifacts.

Compare before/after metrics and visuals

Perform quantitative comparisons for memory/CPU/GC/threading and side-by-side flamegraph analysis.

Document final verification outcome

Create comparison and final results reports with regressions, gains, and reproducible scenario details.

Reference

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

---name: 164-java-profiling-verifydescription: 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. This should trigger for requests such as Verify performance fix; Verify the performance; Verify the memory; Verify the threading. Part of cursor-rules-java projectlicense: Apache-2.0---# 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 - **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 - Verify performance fix - Verify the performance - Verify the memory - Verify the threading - Verify the GC - Verify the profiling - Verify the profiling - Performance benchmark ## Workflow 1. **Read verification reference and confirm baseline data** Read `references/164-java-profiling-verify.md` and verify baseline artifacts exist and are non-empty. 2. **Generate post-refactoring profiling data** Run profiling with identical load/test conditions to produce comparable post-refactoring artifacts. 3. **Compare before/after metrics and visuals** Perform quantitative comparisons for memory/CPU/GC/threading and side-by-side flamegraph analysis. 4. **Document final verification outcome** Create comparison and final results reports with regressions, gains, and reproducible scenario details. ## Reference For detailed guidance, examples, and constraints, see [references/164-java-profiling-verify.md](references/164-java-profiling-verify.md).

Frequently asked questions