Skip to content
Skills Library
Programming · Building & coding

eclipse-edit

/eclipse-edit

Edit files in Eclipse projects using MCP tools. Use this when modifying code in Eclipse workspace projects — it keeps Eclipse editors in sync, triggers incremental compilation, and provides undo via local history.

Licence
MIT
Last repository change
20.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Edit files in Eclipse projects using MCP tools. Use this when modifying code in Eclipse workspace projects — it keeps Eclipse editors in sync, triggers incremental compilation, and provides undo via local history.

Arguments

/eclipse-edit [description of changes]
Original author description

Edit files in Eclipse projects using MCP tools. Use this when modifying code in Eclipse workspace projects — it keeps Eclipse editors in sync, triggers incremental compilation, and provides undo via local history.

How it works

  1. Available Editing Tools
  2. Refactoring Tools
  3. Workflow
  4. Tips
Original SKILL.md headings · 50 lines, 463 words
SKILL.md preview
---
name: eclipse-edit
description: Edit files in Eclipse projects using MCP tools. Use this when modifying code in Eclipse workspace projects — it keeps Eclipse editors in sync, triggers incremental compilation, and provides undo via local history.
argument-hint: "[description of changes]"
allowed-tools: mcp__eclipse-coder__applyPatch, mcp__eclipse-coder__replaceString, mcp__eclipse-coder__insertIntoFile, mcp__eclipse-coder__createFile, mcp__eclipse-coder__deleteFile, mcp__eclipse-coder__deleteLinesInFile, mcp__eclipse-coder__replaceFileContent, mcp__eclipse-coder__formatFile, mcp__eclipse-coder__organizeImports, mcp__eclipse-coder__organizeImportsInPackage, mcp__eclipse-coder__undoEdit, mcp__eclipse-coder__renameFile, mcp__eclipse-coder__createDirectories, mcp__eclipse-coder__moveResource, mcp__eclipse-coder__refactorRenameJavaType, mcp__eclipse-coder__refactorMoveJavaType, mcp__eclipse-coder__refactorRenamePackage, mcp__eclipse-ide__getCompilationErrors, mcp__eclipse-ide__getProjectLayout, mcp__eclipse-ide__readProjectResource, mcp__eclipse-ide__getClassOutline, mcp__eclipse-ide__getMethodSource, mcp__eclipse-ide__getFilteredSource, mcp__eclipse-ide__getSource
---

# Eclipse Code Editing

Edit files in Eclipse workspace projects using the eclipse-coder MCP tools. These tools keep Eclipse editors synchronized, trigger incremental compilation, and maintain local history for undo.

## Available Editing Tools

- **applyPatch** — Atomically apply a unified diff after validating every hunk. It supports multiple hunks and fuzzy context matching, preserves the file's line delimiter, creates an `undoEdit` backup, and can show Eclipse's Apply Patch wizard with `showDialog=true`.
- **replaceString** — Find and replace exact string. Good for single targeted changes. Optionally scoped to a line range.
- **insertIntoFile** — Insert content before a specific line (1-based).
- **createFile** — Create a new file and open it in the editor.
- **deleteFile** — Delete a file from the project.
- **deleteLinesInFile** — Delete a range of lines (1-based, inclusive).
- **replaceFileContent** — Replace entire file content.
- **formatFile** — Format a Java file using Eclipse's formatter (Ctrl+Shift+F).
- **organizeImports** — Organize imports in a Java file (Ctrl+Shift+O).
- **organizeImportsInPackage** — Organize imports across all files in a package.
- **undoEdit** — Restore a file from Eclipse's local history.

Direct file edits return only after Eclipse has synchronized the saved resource, workspace notifications, cached content, JDT compilation unit (for Java files), and editor selection. Check the `Workspace state` line in the result for `saved`, cache/JDT state, and the final modification stamp.

## Refactoring Tools

For Java files, prefer refactoring tools over manual rename/move — they update all references:
- **refactorRenameJavaType** — Rename class/interface/enum with workspace-wide reference updates.
- **refactorMoveJavaType** — Move type to different package with reference updates.
- **refactorRenamePackage** — Rename package with all declaration and reference updates.
- **moveResource** — Move file/folder (no reference updates — use refactorMoveJavaType for Java).

## Workflow

1. **Read efficiently** — Don't dump entire files:
   - `getClassOutline` → understand class structure (~30 lines vs ~300)
   - `getMethodSource` → read only the methods you need to edit
   - `getFilteredSource` → full source with non-relevant methods collapsed
   - `readProjectResource` with `excludeImports=true` → skip import noise
   - Reserve `getSource` / full `readProjectResource` for small files
2. **Edit** using the appropriate tool (see above)
3. **Verify** with `getCompilationErrors` to check for problems
4. **Clean up** with `organizeImports` if new types were referenced, `formatFile` for conventions

## Tips

- For multi-hunk changes, prefer `applyPatch` over multiple `replaceString` calls
- `replaceString` requires exact whitespace matching — if it fails, try `applyPatch` instead
- All tools require `projectName` (Eclipse project name) and `filePath` (relative to project root, without project name)
- Editing tools open/refresh the affected file and reveal the edited line; multi-file refactorings reveal the primary or first changed file
- Use `getProjectLayout` with `scopePath` and `maxDepth` to navigate large projects
- Line numbers from `getClassOutline`, `getMethodSource`, and `getFilteredSource` are always accurate for `replaceString` line ranges and `applyPatch` hunks

Versions

The database has no other skills named eclipse-edit.

Database snapshot: 13.11.2026 · package version 5f32e8b1783c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90eclipse-analyze
    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.
  • 100eclipse
    Expert Eclipse IDE assistance covering Java development (JDT), Maven/Gradle m2e plugins, workspace configuration, and debugging. Use when building and debugging enterprise Java applications.
  • 100eclipse-license-check
    Vet third-party dependencies for an Eclipse Foundation project with the Eclipse Dash License Tool — license checks, "do I need to vet X?" questions, IPLab review filing, and release IP due diligence. Use whenever the user mentions Eclipse license checking, dash-licenses, the…
  • 90dcp-eclipse
    ECLiPSe, the ECLiPSe Constraint Logic Programming system (version 7.x), used through its native Prolog interface (eclipse launcher, .ecl files), for finite-domain constraint satisfaction and optimisation in Prolog syntax with libraries ic, ic_global, gfd (Gecode),…
  • 100edt-mcp-build-test
    How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo. Use when building the plugin, running or writing tests, or verifying a change before committing.
  • 100edt-mcp-build-test
    How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo. Use when building the plugin, running or writing tests, or verifying a change before committing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.