Repository navigation
Closed
Labels
capability:platformFramework / agent substrate skills (install, verify, doctor, override, status, setup bootstrap)Framework / agent substrate skills (install, verify, doctor, override, status, setup bootstrap)enhancementNew feature or requestNew feature or requestfamily:docsDocs, MISSION.md, READMEsDocs, MISSION.md, READMEsfamily:setupsetup-* skillssetup-* skillsfamily:toolstools/*tools/*good first issueGood for newcomersGood for newcomerssubstrate:action-guardTool substrate: deterministic pre-tool-use command guardsTool substrate: deterministic pre-tool-use command guardssubstrate:analyticsTool substrate: read-only metrics / dashboards / renderersTool substrate: read-only metrics / dashboards / rendererssubstrate:framework-devTool substrate: build / validate / eval the framework itselfTool substrate: build / validate / eval the framework itself
Description
Goal: Bring JetBrains Junie to feature parity with Claude Code as a skill runtime. Grounds: RFC-AI-0004 Principle 3 — Vendor neutrality.
Why Junie: JetBrains IDEs cover a large slice of the Java / Kotlin / PyCharm / IntelliJ user base — that includes most of the Apache Java-stack PMCs (Lucene/Solr, Cassandra, Camel, Beam, Flink, Kafka, Pulsar, NetBeans, …). Reaching parity means a maintainer can run framework skills from inside their JetBrains IDE without context-switching to a separate terminal CLI.
What "parity" means:
- Skills under
.claude/skills/<name>/SKILL.mdare invokable from Junie - The
tools/*bridges are reachable — Junie supports shell command execution - Sandbox parity: Junie runs inside the JetBrains IDE process; document threat-model considerations and the mapping to the framework's sandbox baseline (different — IDE-hosted)
- HITL primitives: Junie has per-action confirmation natively — verify and document
Suggested approach:
- Map
SKILL.md→ Junie's.junie/guidelines.mdconvention (Junie reads these natively as project-level agent instructions) - Document skill-invocation: how a maintainer triggers (e.g.)
security-issue-triagefrom inside the JetBrains IDE - Validate which framework skills are well-suited to IDE-hosted execution vs better as terminal CLI flows
Reference:
- RFC-AI-0004:
docs/rfcs/RFC-AI-0004.md - Junie: https://www.jetbrains.com/junie/
.junie/guidelines.mdconvention: https://www.jetbrains.com/help/junie/customize-guidelines.html- Existing skill shape:
.claude/skills/
Metadata
Metadata
Assignees
Labels
capability:platformFramework / agent substrate skills (install, verify, doctor, override, status, setup bootstrap)Framework / agent substrate skills (install, verify, doctor, override, status, setup bootstrap)enhancementNew feature or requestNew feature or requestfamily:docsDocs, MISSION.md, READMEsDocs, MISSION.md, READMEsfamily:setupsetup-* skillssetup-* skillsfamily:toolstools/*tools/*good first issueGood for newcomersGood for newcomerssubstrate:action-guardTool substrate: deterministic pre-tool-use command guardsTool substrate: deterministic pre-tool-use command guardssubstrate:analyticsTool substrate: read-only metrics / dashboards / renderersTool substrate: read-only metrics / dashboards / rendererssubstrate:framework-devTool substrate: build / validate / eval the framework itselfTool substrate: build / validate / eval the framework itself
Activity
potiuk commentedon May 31, 2026
Just work on it.. We do not assign things
potiuk commentedon Sep 10, 2026
Two things that have moved since this was filed, both of which change where a contributor starts.
The skill layout in the body is stale. This points at
.claude/skills/<name>/SKILL.md. The tree now keeps sources inskills/and exposes the harness-neutral.agents/skills/layout — which is what the Codex adapter reads natively. A Junie adapter should target.agents/skills/, not the Claude-specific path; that also means the port inherits the universal layout instead of re-deriving one.Scope clarification worth keeping separate. Running Claude Code inside IntelliJ IDEA / PyCharm already works and needs nothing extra — plugin state lives in one user-scope store shared by every host of the same CLI, so a marketplace added in a terminal is already there in the IDE. That is now documented under JetBrains IDEs in
marketplaces.md. This issue is specifically about Junie, JetBrains' own agent, which does not read Magpie's skills today — a genuine adapter, followingdocs/adapters/add-a-harness.md.The open question the suggested approach glosses over: mapping
SKILL.mdonto.junie/guidelines.mdis a mapping onto project-level instructions, not onto invocable skills. Worth confirming early whether Junie can dispatch a named skill on demand, because if it only ingests guidelines as always-on context, 74 skills is not a viable shape and the port needs a different entry point.feat(plugins): fix Codex install, default-install a set, pre-flight e…
Kaap10 commentedon Nov 15, 2026
The JetBrains Junie runtime documentation, adapter support, and test suite were merged in PR #1666 (commit 6c24f30). Closing this issue as completed.