Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for requests such as Improve the code with documentation; Apply documentation; Refactor the code with documentation. Part of cursor-rules-java project
85
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Generate comprehensive Java project documentation through a modular, step-based interactive process that covers README.md, package-info.java, and Javadoc. This is an interactive SKILL.
What is covered in this Skill?
@param/@return/@throws tags./mvnw clean compile and ./mvnw javadoc:javadocBefore applying any documentation generation, ensure the project validates. If validation fails, stop immediately — do not proceed until all validation errors are resolved.
./mvnw validate or mvn validate before applying any documentation generationRun ./mvnw validate or mvn validate and stop immediately if validation fails.
Read references/170-java-documentation.md and identify required outputs (README, package-info, Javadoc enhancements).
Create or update documentation using the selected file-handling strategy (overwrite/add/backup/skip).
Execute ./mvnw clean compile and ./mvnw javadoc:javadoc (or equivalent) to validate generated docs.
For detailed guidance, examples, and constraints, see references/170-java-documentation.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.