java-launch-troubleshooting Skill
Use when the user wants to run, launch, start, restart, or stop a Java program (main class, Spring Boot, JAR, Maven, Gradle), or diagnose launch failures (mainClass missing, classpath unresolved, compile failure, "project not detected", ClassNotFoundException at startup). NOT for inspecting variables, stepping, or sett Published by microsoft in vscode-java-debug.
What is java-launch-troubleshooting Skill?
Use when the user wants to run, launch, start, restart, or stop a Java program (main class, Spring Boot, JAR, Maven, Gradle), or diagnose launch failures (mainClass missing, classpath unresolved, compile failure, "project not detected", ClassNotFoundException at startup). NOT for inspecting variables, stepping, or sett Published by microsoft in vscode-java-debug. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode-java-debug
Technical details
- Install or run with Copy skill directory
When to use java-launch-troubleshooting Skill
- Use it for developers using vscode-java-debug.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-java-debug
- Skill file: resources/skills/java-launch-troubleshooting/SKILL.md
What it does
Use when the user wants to run, launch, start, restart, or stop a Java program (main class, Spring Boot, JAR, Maven, Gradle), or diagnose launch failures (mainClass missing, classpath unresolved, compile failure, "project not detected", ClassNotFoundException at startup). NOT for inspecting variables, stepping, or sett
Skill instructions
Java Launch Troubleshooting Use this skill when the user wants to start or stop a Java program, or when an attempted launch fails. Typical user phrases: - "run this main class", "start the app", "launch the Spring Boot project", "run the jar" - "stop the debug session", "kill the running app" - prior runinterminal failed with ClassNotFoundException, mainClass is not set, Could not find or load main class, Could not resolve classpath - the user changed pom.xml / build.gradle and the app no longer starts Tools These language model tools are contributed by the Debugger for Java extension and are deferred. Activate them with toolsearchtoolregex using pattern javabreakpoint|debug before first use. | Tool | Purpose | |---|---| | debugjavaapplication | Build + resolve classpath + start JVM. Returns precise compile and classpath errors. | | getdebugsessioninfo | Check whether a debug session is already running and its status. | | stopdebugsession | Stop a running Java debug session cleanly. |
Explore related resources
Frequently asked questions
What is java-launch-troubleshooting?
java-launch-troubleshooting is a open-source AI agent skill with Copy skill directory. Use when the user wants to run, launch, start, restart, or stop a Java program (main class, Spring Boot, JAR, Maven, Gradle), or diagnose launch failures (mainClass missing, classpath.
Who is java-launch-troubleshooting best for?
java-launch-troubleshooting is best for reusing agent instructions, scripts, and references.
How do I install java-launch-troubleshooting?
Install or run java-launch-troubleshooting using Copy skill directory. Check java-launch-troubleshooting for the latest setup command.
Is java-launch-troubleshooting actively maintained?
java-launch-troubleshooting may need a closer maintenance check before production use.
Auto-fetched from GitHub.
