eclipse-plugin

Cursor plugin for the Eclipse team: Forge Rovo agents, pre-push code review, pre-push Snyk (staged scope), and Jira ticket-to-plan workflows.

Contents

Skill	Purpose
forge-rovo-agent	Add a Forge Rovo agent with manifest.yml actions and backend handlers; companion docs in handler-reference.md and manifest-reference.md.
pre-push-code-review	Review staged changes for correctness, security, maintainability, and repo conventions before push.
pre-push-snyk-review	Run Snyk CLI against staged paths (Code; Open Source / IaC when relevant manifests are staged) and report push readiness.
ticket-to-plan	Turn a Jira ticket (MCP or paste) into an implementation plan file under .cursor/plans/ in the workspace.

Layout

This repo follows the Cursor plugins reference:

.cursor-plugin/
└── plugin.json    # manifest
skills/
├── forge-rovo-agent/
│   ├── SKILL.md
│   ├── handler-reference.md
│   └── manifest-reference.md
├── pre-push-code-review/SKILL.md
├── pre-push-snyk-review/SKILL.md
└── ticket-to-plan/SKILL.md

Treat skills/ as the canonical plugin payload. You can add optional plugin roots later (for example rules/, agents/, hooks/, mcp.json) per the same docs.

Local setup

Cursor loads plugins from ~/.cursor/plugins/local/ (each subdirectory is one plugin). Install this repo there so you can edit skills and test changes before publishing.

1. Create the local plugins folder (if it does not exist):

   mkdir -p ~/.cursor/plugins/local

2. Clone this repository into that folder (use your fork URL if you forked it):

   cd ~/.cursor/plugins/local
   git clone https://github.com/appfire-team/eclipse-plugin.git eclipse-plugin

   You should end up with:

   ~/.cursor/plugins/local/eclipse-plugin/
   ├── .cursor-plugin/plugin.json
   └── skills/...
   

3. Update an existing clone when you pull changes:

   cd ~/.cursor/plugins/local/eclipse-plugin
   git pull

4. Reload Cursor so it picks up manifest or skill changes (Command Palette → Developer: Reload Window, or restart Cursor).

5. Confirm the plugin is loaded: open Cursor Settings → Plugins and check that eclipse-plugin appears in the list (local plugins are shown alongside marketplace installs). If it is missing, confirm the folder path and .cursor-plugin/plugin.json, then reload again.

Notes

• Prefer a real directory under local/ for development. Symlinking a plugin folder into ~/.cursor/plugins/local may not load reliably in some Cursor versions.
• After changing skills/*/SKILL.md or .cursor-plugin/plugin.json, reload if the agent does not see updates immediately.

Publish

After pushing to a public Git repository, submit the repo at cursor.com/marketplace/publish.

Optional: fork cursor/plugin-template for extra assets (logo, rules, MCP). This plugin is currently skills-focused.