Agent skill

Eclipse Analyze

by gradusnikov in gradusnikov/eclipse-chatgpt-plugin

Analyze Java code using Eclipse JDT tools — type hierarchy, find references, call hierarchy, compilation errors, quick fixes, and import suggestions.

MITAuto-check passedAgent Workflows

Install Eclipse Analyze

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

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

GitHub CLI
$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-analyze --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-analyze .claude/skills/eclipse-analyze && 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/

Facts

Skill name
eclipse-analyze
GitHub stars
171
Token cost
~1.6k tokens
SKILL.md length
625 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Analyze Java code using Eclipse JDT tools — type hierarchy, find references, call hierarchy, compilation errors, quick fixes, and import suggestions.

  • Works in 5 steps: getClassOutline — Start here. Returns… → getMethodSource — After seeing the… → getFilteredSource — Middle ground:… → …
  • Tasks that involve Codebase onboarding
  • SKILL.md covers Reading Code Efficiently, Navigation & Understanding, Error Analysis and Project Navigation, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Eclipse Analyze is an agent skill from gradusnikov/eclipse-chatgpt-plugin. Analyze Java code using Eclipse JDT tools — type hierarchy, find references, call hierarchy, compilation errors, quick fixes, and import suggestions. Use this to understand code structure before making changes.

Its SKILL.md is about 1.6k 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 Agent Workflows, covering Codebase onboarding. 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 Codebase onboarding

Example prompts

  • “/eclipse-analyze”

Requirements

  • Pre-approved tools (allowed-tools): mcp__eclipse-ide__getClassOutline, mcp__eclipse-ide__getMethodSource, mcp__eclipse-ide__getFilteredSource, mcp__eclipse-ide__getTypeHierarchy, mcp__eclipse-ide__findReferences, mcp__eclipse-ide__getMethodCallHierarchy, mcp__eclipse-ide__getCompilationErrors, mcp__eclipse-ide__getQuickFixes, mcp__eclipse-ide__getImportSuggestions, mcp__eclipse-ide__getJavaDoc, mcp__eclipse-ide__getSource, mcp__eclipse-ide__getProjectLayout, mcp__eclipse-ide__getProjectProperties, mcp__eclipse-ide__readProjectResource, mcp__eclipse-ide__listProjects, mcp__eclipse-ide__getCurrentlyOpenedFile, mcp__eclipse-ide__getEditorSelection, mcp__eclipse-ide__fileSearch, mcp__eclipse-ide__fileSearchRegExp, mcp__eclipse-ide__findFiles, mcp__eclipse-ide__getProjectDependencies, mcp__eclipse-ide__explainTypeResolution, mcp__eclipse-git__gitReadFile, mcp__eclipse-git__gitDiff

Workflow steps

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

  1. getClassOutline — Start here. Returns class declaration, field declarations, method signatures (no bodies), and inner types — all with…
  2. getMethodSource — After seeing the outline, read only the methods you need. Accepts comma-separated methodNames (e.g…
  3. getFilteredSource — Middle ground: returns the full source but collapses methods you don't need to their signatures. Provide methodNames…
  4. getSource — Full source dump. Use only for small classes or when you need everything. Prefer the tools above to save context.
  5. readProjectResource — Read any file by path. Supports startLine/endLine for ranges, showLineNumbers=true for editing, and…

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-ide__getClassOutline
    • mcp__eclipse-ide__getMethodSource
    • mcp__eclipse-ide__getFilteredSource
    • mcp__eclipse-ide__getTypeHierarchy
    • mcp__eclipse-ide__findReferences
    • mcp__eclipse-ide__getMethodCallHierarchy
    • mcp__eclipse-ide__getCompilationErrors
    • mcp__eclipse-ide__getQuickFixes
    • mcp__eclipse-ide__getImportSuggestions
    • mcp__eclipse-ide__getJavaDoc

    …and 14 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 Analyze loads about 1.6k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 625 words of instructions outside code blocks.

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

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). 625 words, ~1,622 tokens.

Download SKILL.mdSave it as .claude/skills/eclipse-analyze/SKILL.md (or your agent's skills folder).
name
eclipse-analyze
description
Analyze Java code using Eclipse JDT tools — type hierarchy, find references, call hierarchy, compilation errors, quick fixes, and import suggestions. Use this to understand code structure before making changes.
allowed-tools
mcp__eclipse-ide__getClassOutline, mcp__eclipse-ide__getMethodSource, mcp__eclipse-ide__getFilteredSource, mcp__eclipse-ide__getTypeHierarchy, mcp__eclipse-ide__findReferences, mcp__eclipse-ide__getMethodCallHierarchy, mcp__eclipse-ide__getCompilationErrors, mcp__eclipse-ide__getQuickFixes, mcp__eclipse-ide__getImportSuggestions, mcp__eclipse-ide__getJavaDoc, mcp__eclipse-ide__getSource, mcp__eclipse-ide__getProjectLayout, mcp__eclipse-ide__getProjectProperties, mcp__eclipse-ide__readProjectResource, mcp__eclipse-ide__listProjects, mcp__eclipse-ide__getCurrentlyOpenedFile, mcp__eclipse-ide__getEditorSelection, mcp__eclipse-ide__fileSearch, mcp__eclipse-ide__fileSearchRegExp, mcp__eclipse-ide__findFiles, mcp__eclipse-ide__getProjectDependencies, mcp__eclipse-ide__explainTypeResolution, mcp__eclipse-git__gitReadFile, mcp__eclipse-git__gitDiff
argument-hint
[class or element to analyze]

Eclipse Code Analysis

Analyze Java code using Eclipse's JDT (Java Development Tools) infrastructure. These tools provide accurate, compiler-level analysis — not text-based guessing.

Reading Code Efficiently

These tools are designed to minimize context window usage. Follow the outline-first pattern:

  1. getClassOutline — Start here. Returns class declaration, field declarations, method signatures (no bodies), and inner types — all with line numbers and the first sentence of each member's Javadoc (an undocumented override reports its supertype's text, flagged javadocInherited). A 500-line class becomes ~30 lines. Provide fullyQualifiedClassName. Set includeFields=false to omit fields; javadoc=FULL renders whole comments, javadoc=NONE leaves them out.

  2. getMethodSource — After seeing the outline, read only the methods you need. Accepts comma-separated methodNames (e.g., "save,findById,delete"). Returns source with line numbers. Set includeJavadoc=false to skip doc comments. Use methodSignature to disambiguate overloads (e.g., "String" matches methods with a String parameter).

  3. getFilteredSource — Middle ground: returns the full source but collapses methods you don't need to their signatures. Provide methodNames to expand specific methods; all others are shown as one-line signatures with line ranges. Set excludeImports=true (the default) to collapse the import block. Line numbers always match the original file for accurate editing.

  4. getSource — Full source dump. Use only for small classes or when you need everything. Prefer the tools above to save context.

  5. readProjectResource — Read any file by path. Supports startLine/endLine for ranges, showLineNumbers=true for editing, and excludeImports=true to collapse Java import blocks.

Choosing the Right Tool
ScenarioToolWhy
Understand class structuregetClassOutlineSignatures only, ~90% smaller
Read 1-3 specific methodsgetMethodSourceSurgical reads with line numbers
Read class but focus on 2 methodsgetFilteredSourceFull context, collapsed noise
Small class (<100 lines)getSourceOverhead not worth optimizing
Referenced-library classgetSourceUses attached source or decompiles the class
Diagnose which JAR/root wonexplainTypeResolutionShows the project-specific JDT classpath decision
Compare a historical filegitReadFileReads a revision or staged index without checkout
Non-Java file or specific line rangereadProjectResourceWorks with any file type
Show full SKILL.md (301 more words)Show less

Navigation & Understanding

  • getTypeHierarchy — Show supertypes, implemented interfaces, and subtypes for a class.
  • findReferences — Find all usages of a type, method, or field across the workspace. Essential before renaming or deleting.
  • getMethodCallHierarchy — Show callers and callees of a method. Use methodSignature for overloaded methods.
  • getJavaDoc — Rendered Javadoc (Markdown) of a type and each of its members, as the IDE hover shows it, inherited text included. memberName narrows it to one member's overloads; javadoc=SUMMARY gives first sentences only. getTypeHierarchy, searchTypes, searchMethods and getPackageSummary take the same javadoc parameter.
  • explainTypeResolution — Explain source-vs-binary resolution in one project, including classpath root/entry, source attachment, class file, and whether getSource will decompile.
  • gitReadFile — Read a project-relative text file at a Git revision or from INDEX without modifying the working tree.
  • gitDiff — Limit diffs with project-relative pathFilter values and optionally set ignoreWhitespace=true.

Error Analysis

  • getCompilationErrors — Get all compilation errors/warnings. Filter by projectName and severity (ERROR, WARNING, ALL).
  • getQuickFixes — Get available quick fixes for errors in a file. Optionally filter by lineNumber.
  • getImportSuggestions — Find import candidates for unresolved types.

Project Navigation

  • getProjectLayout — File/folder structure. Use scopePath and maxDepth for large projects.
  • getProjectProperties — Java version, source folders, output location, natures.
  • listProjects — All workspace projects with their natures.
  • getProjectDependencies — Maven dependencies for a project.
  • fileSearch — Plain text search across workspace files. Filter with fileNamePatterns.
  • fileSearchRegExp — Regex search across workspace files.
  • findFiles — Find files by glob patterns (e.g., *.xml, pom.xml).

Editor Context

  • getCurrentlyOpenedFile — Get the file currently active in the Eclipse editor.
  • getEditorSelection — Get the currently selected text/lines in the active editor.
  1. Orient: listProjects or getProjectLayout to find what you need
  2. Outline: getClassOutline to understand class structure
  3. Focus: getMethodSource to read specific methods, or getFilteredSource for full-but-collapsed view
  4. Analyze: getTypeHierarchy, findReferences, getMethodCallHierarchy as needed
  5. After edits: getCompilationErrors to verify, then getQuickFixes or getImportSuggestions to resolve

© gradusnikov, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

Open the folder on GitHubat commit b789344

Compare with similar skills

Eclipse Analyze 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 Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Eclipse Analyze this skillgradusnikov/eclipse-chatgpt-plugin171—~1.6kAutomated safety check: PassMIT
Codebase SearchHelweg/open-codebase-index217—~1.3kAutomated safety check: PassMIT
Codebase Search WorkflowHelweg/open-codebase-index217—~822Automated safety check: PassMIT
1c Code Searchcomol/ai_rules_1c480—~1kAutomated safety check: PassNone
Basemind Index ScanGoldziher/basemind106—~997Automated safety check: WarnMIT
Drydock Repo Harness SetupYeachan-Heo/oh-my-claudecode40k—~5.2kAutomated safety check: PassMIT

Similar skills

  • Codebase Search

    Helweg/open-codebase-index

    Chooses the right retrieval tool for code questions: compact context for unfamiliar repos, direct lookup for known symbols, call graphs for relationships and grep for exhaustive matches.

    217 GitHub stars~1.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Codebase Search Workflow

    Helweg/open-codebase-index

    Directs an agent to use a local codebase index for repository orientation, definition lookups, call graphs and semantic search before turning to web lookups.

    217 GitHub stars~822 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • 1c Code Search

    comol/ai_rules_1c

    Find BSL code in a 1C project — routines by name, code by behaviour or exact literal, module layout, members of a context — through the graph and code-metadata MCP servers before any Grep.

    480 GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Basemind Index Scan

    Goldziher/basemind

    Builds or refreshes the basemind code index from the command line, for when basemind reports no index or its MCP server is not running.

    106 GitHub stars~997 tokensUpdated today
    Agent WorkflowsAuto-check: warnings
  • Drydock Repo Harness Setup

    Yeachan-Heo/oh-my-claudecode

    Sets up a shared repo environment for people and agents: CLAUDE.md, a CONTEXT.md glossary, ADRs, standards and a design-system folder, and audits drift with --check.

    40k GitHub stars~5.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Edt MCP Architecture

    DitriXNew/EDT-MCP

    Map of the EDT-MCP plugin's target architecture — where the shared helpers live, the layering rules, and the canonical way to do project/metadata/code resolution.

    295 GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from gradusnikov/eclipse-chatgpt-plugin

  • Eclipse Debug

    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.

    171 GitHub stars~1.3k tokensUpdated 10 days ago
    Auto-check passed
  • Eclipse Edit

    gradusnikov/eclipse-chatgpt-plugin

    Edit files in Eclipse projects using MCP tools. An agent skill from gradusnikov/eclipse-chatgpt-plugin.

    171 GitHub stars~1.1k tokensUpdated 10 days ago
    Auto-check passed
  • Eclipse Run

    gradusnikov/eclipse-chatgpt-plugin

    Launch and stop Java applications in Eclipse. An agent skill from gradusnikov/eclipse-chatgpt-plugin.

    171 GitHub stars~780 tokensUpdated 10 days ago
    Auto-check passed
  • Eclipse Test

    gradusnikov/eclipse-chatgpt-plugin

    Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods.

    171 GitHub stars~1k tokensUpdated 10 days ago
    Auto-check passed

Questions about Eclipse Analyze

What does Eclipse Analyze do?

Analyze Java code using Eclipse JDT tools — type hierarchy, find references, call hierarchy, compilation errors, quick fixes, and import suggestions. Eclipse Analyze is an agent skill from gradusnikov/eclipse-chatgpt-plugin. Analyze Java code using Eclipse JDT tools — type hierarchy, find references, call hierarchy, compilation errors, quick fixes, and import suggestions.

When should I use Eclipse Analyze?

Eclipse Analyze fits situations like: tasks that involve Codebase onboarding.

How do I install Eclipse Analyze in Claude Code?

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

How do I install Eclipse Analyze in Codex?

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

Can I use Eclipse Analyze 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-analyze -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-analyze, .gemini/skills/eclipse-analyze, .github/skills/eclipse-analyze and .opencode/skills/eclipse-analyze in your project.

What does Eclipse Analyze need to run?

SKILL.md names no scripts, command-line tools or credentials: Eclipse Analyze is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__eclipse-ide__getClassOutline, mcp__eclipse-ide__getMethodSource, mcp__eclipse-ide__getFilteredSource, mcp__eclipse-ide__getTypeHierarchy, mcp__eclipse-ide__findReferences, mcp__eclipse-ide__getMethodCallHierarchy, mcp__eclipse-ide__getCompilationErrors, mcp__eclipse-ide__getQuickFixes, mcp__eclipse-ide__getImportSuggestions, mcp__eclipse-ide__getJavaDoc, mcp__eclipse-ide__getSource, mcp__eclipse-ide__getProjectLayout, mcp__eclipse-ide__getProjectProperties, mcp__eclipse-ide__readProjectResource, mcp__eclipse-ide__listProjects, mcp__eclipse-ide__getCurrentlyOpenedFile, mcp__eclipse-ide__getEditorSelection, mcp__eclipse-ide__fileSearch, mcp__eclipse-ide__fileSearchRegExp, mcp__eclipse-ide__findFiles, mcp__eclipse-ide__getProjectDependencies, mcp__eclipse-ide__explainTypeResolution, mcp__eclipse-git__gitReadFile, mcp__eclipse-git__gitDiff.

Does Eclipse Analyze 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 Analyze 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 Analyze use?

Eclipse Analyze 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 Analyze use?

About 1.6k tokens (SKILL.md is roughly 6.5k 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 Analyze?

Skills that share tags, products or a category with Eclipse Analyze: Codebase Search (Helweg/open-codebase-index, 217 stars), Codebase Search Workflow (Helweg/open-codebase-index, 217 stars), 1c Code Search (comol/ai_rules_1c, 480 stars) and Basemind Index Scan (Goldziher/basemind, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eclipse Analyze?

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.