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; Generate README or developer documentation for a Java project; Document Java APIs architecture or project workflows. Part of Plinth Toolkit
65
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/170-java-documentation/SKILL.mdGenerate 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.
77b8825
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.