Use when you need to refactor Java code based on profiling analysis findings — including reviewing docs/profiling-problem-analysis and docs/profiling-solutions, identifying specific performance bottlenecks, and implementing targeted code changes to address CPU, memory, or threading issues. This should trigger for requests such as Refactor the code with profiling; Apply profiling; Refactor the code with profiling; Optimize hot path. Part of cursor-rules-java project
85
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Implement refactoring based on profiling analysis: review profiling-problem-analysis-YYYYMMDD.md and profiling-solutions-YYYYMMDD.md, identify specific performance bottlenecks, and refactor code to fix them. Ensure all tests pass after changes.
What is covered in this Skill?
Scope: Changes must pass all tests. Apply fixes incrementally and verify after each significant change.
Verify that changes pass all tests before considering the refactoring complete.
./mvnw clean verify or mvn clean verify after applying refactoringRead docs/profiling-problem-analysis-YYYYMMDD.md and docs/profiling-solutions-YYYYMMDD.md to select target bottlenecks.
Implement focused code changes for documented CPU, memory, or threading hotspots, incrementally and safely.
Run ./mvnw clean verify or mvn clean verify; if tests fail, fix issues before continuing.
Summarize implemented changes and expected metric improvements for Step 4 comparison.
For detailed guidance, examples, and constraints, see references/163-java-profiling-refactor.md.
762cb86
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.