jvm-tooling-workflows

Select the smallest official JDK tool for compilation, runtime, documentation, and packaging workflows.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ririnto/sinon --skill jvm-tooling-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jvm-tooling-workflows
Source: https://github.com/ririnto/sinon/tree/main/plugins/jvm/skills/jvm-tooling-workflows
Command: npx skills add https://github.com/ririnto/sinon --skill jvm-tooling-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers to use the smallest official JDK tool to accomplish a given task, instead of relying on wrappers that obscure the tool chain.

Core Features & Use Cases

  • Direct tool sequences: javac, java, javadoc, and jdeps for core compilation, running, documentation, and dependency analysis workflows.
  • Version-gated guidance: covers JDK 8/11/17/21/25 LTS lines; clarifies when jshell, jlink, and jpackage are standard or incubating.
  • Safe, repeatable workflows: emphasizes validating tool availability and module boundaries before packaging or runtime image creation.

Quick Start

Start by selecting the smallest official JDK tool that advances your goal, for example compile with javac and run with java.

Frequently Asked Questions about jvm-tooling-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a custom Java runtime image using jlink?

To create a custom Java runtime image with jlink, first run jdeps to analyze module dependencies and boundaries, then use jlink to produce a reliable, minimized runtime image for your application.

What is the smallest official JDK tool to compile and run Java code?

The smallest official JDK tools to compile and run Java code are javac for direct compilation and java for running the application, avoiding unnecessary wrapper overhead in the toolchain.

Can I use jpackage and jshell across all LTS JDK versions?

Availability of jshell, jlink, and jpackage depends on the LTS line, such as JDK 8, 11, 17, 21, or 25. Version-gated guidance clarifies when these tools are standard or incubating features.

How do I analyze Java module dependencies before packaging?

Analyze Java module dependencies before packaging by using jdeps, which verifies tool availability and module awareness, forming a required jdeps-before-jlink workflow for reliable packaging.

Why should I run jdeps before creating a runtime image with jlink?

Running jdeps before jlink validates tool availability and module boundaries, ensuring you produce reliable runtime images or installers instead of broken or incomplete packages.