Agent skill

Eclipse Debug

by gradusnikov in gradusnikov/eclipse-chatgpt-plugin

Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes.

MITAuto-check passedFrontend & Design

Install Eclipse Debug

skills CLI

$ npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-debug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/eclipse-debug .claude/skills/eclipse-debug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "eclipse-debug" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-debug into .claude/skills/eclipse-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-debug", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-debug

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-debug --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/eclipse-debug .agents/skills/eclipse-debug && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "eclipse-debug" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-debug into .agents/skills/eclipse-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-debug", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-debug --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/eclipse-debug .cursor/skills/eclipse-debug && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "eclipse-debug" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-debug into .cursor/skills/eclipse-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-debug", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/gradusnikov/eclipse-chatgpt-plugin.git --path .claude/skills/eclipse-debug

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-debug --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/eclipse-debug .gemini/skills/eclipse-debug && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "eclipse-debug" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-debug into .gemini/skills/eclipse-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-debug", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-debug

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/eclipse-debug .github/skills/eclipse-debug && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "eclipse-debug" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-debug into .github/skills/eclipse-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-debug", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-debug --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/eclipse-debug .opencode/skills/eclipse-debug && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "eclipse-debug" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-debug into .opencode/skills/eclipse-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-debug", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: eclipse-debug
GitHub stars: 171
Token cost: ~1.3k tokens
SKILL.md length: 434 words
Files: 1
Skills in repo: 5
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes.

Works in 7 steps: Set breakpoints where you want to pause → Launch in debug mode → Wait for breakpoint hit, then inspect → …
Tasks that involve Responsive design
SKILL.md covers Breakpoints, Launch, Stepping (requires suspended… and Inspection (requires suspended…, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Eclipse Debug is an agent skill from gradusnikov/eclipse-chatgpt-plugin. Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Responsive design and Debugging. It works with Java and Model Context Protocol. The repository describes itself as: Eclipse IDE as an MCP Server for AI Agents. The licence is MIT.

When your agent uses it

Tasks that involve Responsive design
Tasks that involve Debugging

Example prompts

“/eclipse-debug”

Requirements

Pre-approved tools (allowed-tools): mcp__eclipse-runner__debugJavaApplication, mcp__eclipse-runner__launchConfiguration, mcp__eclipse-runner__listLaunchConfigurations, mcp__eclipse-runner__stopApplication, mcp__eclipse-runner__listActiveLaunches, mcp__eclipse-runner__toggleBreakpoint, mcp__eclipse-runner__setConditionalBreakpoint, mcp__eclipse-runner__listBreakpoints, mcp__eclipse-runner__removeAllBreakpoints, mcp__eclipse-runner__getStackTrace, mcp__eclipse-runner__evaluateExpression, mcp__eclipse-runner__resumeDebug, mcp__eclipse-runner__stepOver, mcp__eclipse-runner__stepInto, mcp__eclipse-runner__stepReturn, mcp__eclipse-runner__hotCodeReplace, mcp__eclipse-ide__getConsoleOutput, mcp__eclipse-pde__restartMcpServers, mcp__eclipse-pde__reloadWorkspaceBundle

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Set breakpoints where you want to pause
Launch in debug mode
Wait for breakpoint hit, then inspect
Evaluate expressions to understand state
Step through code
Fix code and hot-swap without restarting
Clean up

What it can do on your machine

Read from SKILL.md and the folder at commit b789344. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- mcp__eclipse-runner__debugJavaApplication
- mcp__eclipse-runner__launchConfiguration
- mcp__eclipse-runner__listLaunchConfigurations
- mcp__eclipse-runner__stopApplication
- mcp__eclipse-runner__listActiveLaunches
- mcp__eclipse-runner__toggleBreakpoint
- mcp__eclipse-runner__setConditionalBreakpoint
- mcp__eclipse-runner__listBreakpoints
- mcp__eclipse-runner__removeAllBreakpoints
- mcp__eclipse-runner__getStackTrace
…and 9 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Eclipse Debug loads about 1.3k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 434 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~45
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gradusnikov/eclipse-chatgpt-plugin at commit b789344, republished under its MIT licence (© gradusnikov). 434 words, ~1,269 tokens.

Download SKILL.mdSave it as .claude/skills/eclipse-debug/SKILL.md (or your agent's skills folder).

name: eclipse-debug
description: Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes.
allowed-tools: mcp__eclipse-runner__debugJavaApplication, mcp__eclipse-runner__launchConfiguration, mcp__eclipse-runner__listLaunchConfigurations, mcp__eclipse-runner__stopApplication, mcp__eclipse-runner__listActiveLaunches, mcp__eclipse-runner__toggleBreakpoint, mcp__eclipse-runner__setConditionalBreakpoint, mcp__eclipse-runner__listBreakpoints, mcp__eclipse-runner__removeAllBreakpoints, mcp__eclipse-runner__getStackTrace, mcp__eclipse-runner__evaluateExpression, mcp__eclipse-runner__resumeDebug, mcp__eclipse-runner__stepOver, mcp__eclipse-runner__stepInto, mcp__eclipse-runner__stepReturn, mcp__eclipse-runner__hotCodeReplace, mcp__eclipse-ide__getConsoleOutput, mcp__eclipse-pde__restartMcpServers, mcp__eclipse-pde__reloadWorkspaceBundle
argument-hint: [project] [main class]

Debug Java Applications in Eclipse

Full interactive debugging using Eclipse's JDT debugger. Set breakpoints, step through code, inspect variables, evaluate expressions, and hot-swap changes.

Breakpoints

toggleBreakpoint — Set or remove a line breakpoint. Provide projectName, typeName (fully qualified), and lineNumber.
setConditionalBreakpoint — Set a breakpoint with a condition. Only triggers when the condition is true. Also supports hitCount (trigger after N hits).
listBreakpoints — Show all breakpoints with location, enabled status, and conditions.
removeAllBreakpoints — Clear all breakpoints.

Launch

debugJavaApplication — Launch in debug mode. Same parameters as runJavaApplication but defaults to timeout=0 (background). The app stops at breakpoints.
launchConfiguration — Debug an existing saved launch configuration by name with mode="debug", preserving its classpath, VM args, environment variables, working directory, and agent settings (e.g. JRebel). Use listLaunchConfigurations to find the name. Breakpoints set via toggleBreakpoint still apply.

Stepping (requires suspended thread)

stepOver — Execute current line, don't enter method calls.
stepInto — Enter the method call on the current line.
stepReturn — Run until the current method returns.
resumeDebug — Continue execution until next breakpoint or termination.

Inspection (requires suspended thread)

getStackTrace — Show all threads with call stack. For the top frame, also shows local variables with their values and types.
evaluateExpression — Evaluate any Java expression in the context of the suspended frame. Examples: myList.size(), x + y, this.toString(), System.getProperty("user.dir").

Hot Code Replace

hotCodeReplace — Push code changes into the running debug session without restarting. Triggers an incremental build and the JVM reloads changed classes.

Show full SKILL.md (222 more words)Show less

Structural Reloads

restartMcpServers — Rebuild the HTTP MCP server registry after a 500–30,000 ms delay. The delay lets the invoking response complete; clients may need to reconnect.
reloadWorkspaceBundle — Schedule an OSGi update for a bundle whose symbolic name maps to an open workspace project. System bundles, fragments, and installed-only bundles are rejected.
Use hotCodeReplace for supported method-body changes. Use reloadWorkspaceBundle when structural changes (new methods, fields, or MCP tools) cannot be hot-swapped, then restartMcpServers if the HTTP registry still needs rebuilding.

Typical Debug Workflow

Set breakpoints where you want to pause:

toggleBreakpoint(projectName="myapp", typeName="com.example.Main", lineNumber="42")

Launch in debug mode:

debugJavaApplication(projectName="myapp", mainClass="com.example.Main", timeout="0")

Wait for breakpoint hit, then inspect:
```
getStackTrace(nameOrClass="Main")
```

Evaluate expressions to understand state:

evaluateExpression(nameOrClass="Main", expression="myList.size()")

Step through code:

stepOver(nameOrClass="Main")
getStackTrace(nameOrClass="Main")

Fix code and hot-swap without restarting:

# ... edit the file using eclipse-coder tools ...
hotCodeReplace(nameOrClass="Main")
resumeDebug(nameOrClass="Main")

Clean up:

stopApplication(nameOrClass="Main")
removeAllBreakpoints()

Notes

All stepping/inspection tools match debug sessions by substring against the launch name or main class (nameOrClass parameter)
getStackTrace shows local variables only for the top frame to keep output manageable
evaluateExpression has a 10-second timeout
Hot code replace works on most JVMs but has limitations (can't change method signatures or add/remove fields in some cases)
Reload tools are deliberately deferred and may disconnect MCP clients; do not use them while another critical MCP operation is in flight

Files

Just SKILL.md in .claude/skills/eclipse-debug of gradusnikov/eclipse-chatgpt-plugin.

Open the folder on GitHubat commit b789344

Compare with similar skills

Eclipse Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Eclipse Debug compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Eclipse Debug this skillgradusnikov/eclipse-chatgpt-plugin	171	—	~1.3k	Automated safety check: Pass	MIT	9 days ago
Java DebugAmplicode/spring-skills	126	—	~2.7k	Automated safety check: Pass	None	1 mo ago
MCP Debuggerdebugmcp/mcp-debugger	171	—	~3.8k	Automated safety check: Pass	MIT	yesterday
Gearcoleco Debuggingdrhelius/Gearcoleco	141	—	~3.5k	Automated safety check: Pass	GPL-3.0	yesterday
Dbgtheodo-group/debug-that	158	—	~1.9k	Automated safety check: Pass	MIT	4 mo ago
Ue Live DebuggingJasonMa0012/MooaToon	749	—	~2.9k	Automated safety check: Notes	Custom licence	19 days ago

Similar skills

Java Debug
Amplicode/spring-skills
Safety rules, workflows, and tool reference for debugging applications via IntelliJ debugger: breakpoints, debug sessions, stepping, evaluating expressions, inspecting runtime state.
126 GitHub stars~2.7k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
MCP Debugger
debugmcp/mcp-debugger
A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…
171 GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed
Gearcoleco Debugging
drhelius/Gearcoleco
Debug and trace ColecoVision and Super Game Module games using the Gearcoleco emulator MCP server.
141 GitHub stars~3.5k tokensUpdated yesterday
DevelopmentAuto-check passed
Dbg
theodo-group/debug-that
Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.
158 GitHub stars~1.9k tokensUpdated 4 mo ago
DevelopmentAuto-check passed
Ue Live Debugging
JasonMa0012/MooaToon
A skill your agent uses when debugging UE C++ crashes, runtime bugs, or unexpected behavior with Rider MCP available.
749 GitHub stars~2.9k tokensUpdated 19 days ago
DevelopmentAuto-check: notes
Tui Bug Hunt
uw-syfi/vibesys
Drive the VibeSys terminal UI (TUI) headlessly via tmux against real Claude-Code-provider runs, to find and report display bugs, frontend/interaction glitches, backend/protocol problems, and…
103 GitHub stars~6.5k tokensUpdated yesterday
Frontend & DesignAuto-check passed

Questions about Eclipse Debug

What does Eclipse Debug do?

Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes. Eclipse Debug is an agent skill from gradusnikov/eclipse-chatgpt-plugin. Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes.

When should I use Eclipse Debug?

Eclipse Debug fits situations like: tasks that involve Responsive design; tasks that involve Debugging.

How do I install Eclipse Debug in Claude Code?

Run `npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a claude-code`. Or copy the skill folder (.claude/skills/eclipse-debug in gradusnikov/eclipse-chatgpt-plugin) into .claude/skills/eclipse-debug in your project. Claude Code loads it when a task matches its description.

How do I install Eclipse Debug in Codex?

Run `npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a codex`. Or copy the skill folder (.claude/skills/eclipse-debug in gradusnikov/eclipse-chatgpt-plugin) into .agents/skills/eclipse-debug in your project. Codex loads it when a task matches its description.

Can I use Eclipse Debug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eclipse-debug, .gemini/skills/eclipse-debug, .github/skills/eclipse-debug and .opencode/skills/eclipse-debug in your project.

What does Eclipse Debug need to run?

SKILL.md names no scripts, command-line tools or credentials: Eclipse Debug is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__eclipse-runner__debugJavaApplication, mcp__eclipse-runner__launchConfiguration, mcp__eclipse-runner__listLaunchConfigurations, mcp__eclipse-runner__stopApplication, mcp__eclipse-runner__listActiveLaunches, mcp__eclipse-runner__toggleBreakpoint, mcp__eclipse-runner__setConditionalBreakpoint, mcp__eclipse-runner__listBreakpoints, mcp__eclipse-runner__removeAllBreakpoints, mcp__eclipse-runner__getStackTrace, mcp__eclipse-runner__evaluateExpression, mcp__eclipse-runner__resumeDebug, mcp__eclipse-runner__stepOver, mcp__eclipse-runner__stepInto, mcp__eclipse-runner__stepReturn, mcp__eclipse-runner__hotCodeReplace, mcp__eclipse-ide__getConsoleOutput, mcp__eclipse-pde__restartMcpServers, mcp__eclipse-pde__reloadWorkspaceBundle.

Does Eclipse Debug access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Eclipse Debug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Eclipse Debug use?

Eclipse Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Eclipse Debug use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Eclipse Debug?

Skills that share tags, products or a category with Eclipse Debug: Java Debug (Amplicode/spring-skills, 126 stars), MCP Debugger (debugmcp/mcp-debugger, 171 stars), Gearcoleco Debugging (drhelius/Gearcoleco, 141 stars) and Dbg (theodo-group/debug-that, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eclipse Debug?

gradusnikov (a GitHub user) maintains it in gradusnikov/eclipse-chatgpt-plugin, which has 171 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 28, 2026.

Source: gradusnikov/eclipse-chatgpt-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Eclipse Debug

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Debug Java Applications in Eclipse

Breakpoints

Launch

Stepping (requires suspended thread)

Inspection (requires suspended thread)

Hot Code Replace

Structural Reloads

Typical Debug Workflow

Notes

Files

Compare with similar skills

Similar skills

More from gradusnikov/eclipse-chatgpt-plugin

Related

Questions about Eclipse Debug