163-java-profiling-refactor
This skill guides developers through the third step of Java performance optimization by reviewing profiling analysis documents, identifying specific bottlenecks in CPU, memory, or threading, and implementing targeted refactors to address them. Use it when you have completed profiling analysis and need to safely apply code changes while ensuring all tests pass before considering the refactoring complete.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/163-java-profiling-refactor && cp -r /tmp/163-java-profiling-refactor/skills/163-java-profiling-refactor ~/.claude/skills/163-java-profiling-refactorSKILL.md
# Java Profiling Workflow / Step 3 / Refactor code to fix 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?** - Review analysis notes: docs/profiling-problem-analysis-YYYYMMDD.md, docs/profiling-solutions-YYYYMMDD.md - Identify specific bottlenecks from the documented findings - Refactor code to address CPU hotspots, memory leaks, threading issues, or other performance problems - Run verification: ./mvnw clean verify or mvn clean verify **Scope:** Changes must pass all tests. Apply fixes incrementally and verify after each significant change. ## Constraints Verify that changes pass all tests before considering the refactoring complete. - **MANDATORY**: Run `./mvnw clean verify` or `mvn clean verify` after applying refactoring - **SAFETY**: If tests fail, fix issues before proceeding - **BEFORE APPLYING**: Read the analysis and solutions documents for specific recommendations - **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 - Refactor the code with profiling - Apply profiling - Refactor the code with profiling - Optimize hot path - Performance refactoring ## Workflow 1. **Review profiling analysis artifacts** Read `docs/profiling-problem-analysis-YYYYMMDD.md` and `docs/profiling-solutions-YYYYMMDD.md` to select target bottlenecks. 2. **Apply targeted performance refactors** Implement focused code changes for documented CPU, memory, or threading hotspots, incrementally and safely. 3. **Verify behavior and performance build integrity** Run `./mvnw clean verify` or `mvn clean verify`; if tests fail, fix issues before continuing. 4. **Prepare handoff for verification phase** Summarize implemented changes and expected metric improvements for Step 4 comparison. ## Reference For detailed guidance, examples, and constraints, see [references/163-java-profiling-refactor.md](references/163-java-profiling-refactor.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