java-debug-inspection Skill
Use when inspecting a Java program that is already being debugged — read local variables, walk the call stack, list threads, evaluate expressions, step in/over/out, continue execution, or set / remove breakpoints in an active Java debug session. NOT for starting, launching, or stopping a debug session — use java-launch Published by microsoft in vscode-java-debug.
What is java-debug-inspection Skill?
Use when inspecting a Java program that is already being debugged — read local variables, walk the call stack, list threads, evaluate expressions, step in/over/out, continue execution, or set / remove breakpoints in an active Java debug session. NOT for starting, launching, or stopping a debug session — use java-launch 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
- Design and media
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use java-debug-inspection Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-java-debug
- Skill file: resources/skills/java-debug-inspection/SKILL.md
What it does
Use when inspecting a Java program that is already being debugged — read local variables, walk the call stack, list threads, evaluate expressions, step in/over/out, continue execution, or set / remove breakpoints in an active Java debug session. NOT for starting, launching, or stopping a debug session — use java-launch
Skill instructions
Java Debug Inspection Use this skill when a Java debug session is already active (the user has launched the program with debugjavaapplication or via the VS Code Run/Debug UI) and they want to observe or steer the running program. Typical user phrases: - "what's the value of user.id right now?", "show me the local variables" - "evaluate list.size()", "what does service.findById(42) return at this frame?" - "show the stack trace", "what threads are running?", "go up one frame" - "step in", "step over", "step out", "continue", "resume" - "set a breakpoint at OrderService.placeOrder", "remove the breakpoint on line 42" If no debug session is active, this skill should not be used — load java-launch-troubleshooting first to start one. 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 | |---|---| | getdebugvariables | Read local varia
Explore related resources
Frequently asked questions
What is java-debug-inspection?
java-debug-inspection is a open-source AI agent skill with Copy skill directory. Use when inspecting a Java program that is already being debugged — read local variables, walk the call stack, list threads, evaluate expressions, step in/over/out, continue execution, or set /.
Who is java-debug-inspection best for?
java-debug-inspection is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install java-debug-inspection?
Install or run java-debug-inspection using Copy skill directory. Check java-debug-inspection for the latest setup command.
Is java-debug-inspection actively maintained?
java-debug-inspection may need a closer maintenance check before production use.
Auto-fetched from GitHub.
