Skip to content

chore: generate Codex, Cursor, and Antigravity plugin manifests#124

Merged
amondnet merged 1 commit into
mainfrom
chore/multi-runtime-plugin-manifests
Jul 8, 2026
Merged

chore: generate Codex, Cursor, and Antigravity plugin manifests#124
amondnet merged 1 commit into
mainfrom
chore/multi-runtime-plugin-manifests

Conversation

@amondnet

@amondnet amondnet commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Summary

Generated via the plugin-dev plugin's multi-format generator, using .claude-plugin/plugin.json as the source of truth. Adds runtime manifests for the ask plugin so it loads in Codex, Cursor, and Antigravity in addition to Claude Code.

Changes

  • .codex-plugin/plugin.json — new Codex runtime manifest
  • .cursor-plugin/plugin.json — new Cursor runtime manifest
  • plugin.json — new Antigravity root manifest
  • hooks.json — new Antigravity root hooks (mirrors hooks/hooks.json, with ${CLAUDE_PLUGIN_ROOT}/ rewritten to ./)
  • release-please-config.json — added the three new version-bearing manifests to the root ask-plugin package's extra-files, so their $.version stays synced with .claude-plugin/plugin.json on release

No MCP servers are declared for this plugin, so no .mcp.json was generated.

Test Plan

  • Verified generated manifest JSON is well-formed and metadata (name, version, description, repo/homepage links) matches .claude-plugin/plugin.json
  • Confirmed release-please-config.json extra-files wiring includes all three new manifests

Related Issues

None — no linked issue for this chore.


Summary by cubic

Generated runtime manifests for the ask plugin so it loads in Codex, Cursor, and Antigravity, and synced their versions via release-please.

  • New Features
    • Added .codex-plugin/plugin.json and .cursor-plugin/plugin.json.
    • Added Antigravity plugin.json and hooks.json (mirrors hooks/hooks.json with path rewrite).
    • Updated release-please-config.json to keep new manifests’ $.version aligned with .claude-plugin/plugin.json.

Written for commit 60091a1. Summary will update on new commits.

Generated via the plugin-dev multi-format generator from
.claude-plugin/plugin.json (source of truth):

- .codex-plugin/plugin.json — Codex runtime manifest
- .cursor-plugin/plugin.json — Cursor runtime manifest
- plugin.json — Antigravity root manifest
- hooks.json — Antigravity root hooks (mirrors hooks/hooks.json with
  ${CLAUDE_PLUGIN_ROOT}/ rewritten to ./)

No MCP servers are declared, so no .mcp.json was generated.

release-please-config.json's extra-files for the root ask-plugin
package now include all three new version-bearing manifests, so their
$.version stays synced with .claude-plugin/plugin.json on release.
@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jul 8, 2026
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@amondnet, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2e7fe856-9e6e-4127-a6e1-4a6acd7eb309

📥 Commits

Reviewing files that changed from the base of the PR and between 9ce5801 and 60091a1.

📒 Files selected for processing (5)
  • .codex-plugin/plugin.json
  • .cursor-plugin/plugin.json
  • hooks.json
  • plugin.json
  • release-please-config.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/multi-runtime-plugin-manifests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@dosubot dosubot Bot added the type:chore Maintenance, build, dependencies label Jul 8, 2026
@sonarqubecloud

sonarqubecloud Bot commented Jul 8, 2026

Copy link
Copy Markdown

@codecov

codecov Bot commented Jul 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@greptile-apps

greptile-apps Bot commented Jul 8, 2026

Copy link
Copy Markdown

Greptile Summary

This PR adds generated plugin manifests for more runtimes.

  • New Codex plugin manifest under .codex-plugin/.
  • New Cursor plugin manifest under .cursor-plugin/.
  • New root Antigravity manifest and hooks file.
  • Release-please version syncing for the new manifests.

Confidence Score: 4/5

The new runtime manifests are mostly straightforward, but the Antigravity hook path can break outside the plugin root.

  • The release version wiring matches the existing manifest update pattern.
  • The root hook command can resolve against the user's workspace and miss the plugin script.
  • The Cursor manifest may not expose Ask as a skill if Cursor relies on capability metadata.

hooks.json, .cursor-plugin/plugin.json

Important Files Changed

Filename Overview
.codex-plugin/plugin.json Adds Codex plugin metadata with an interface block and Skill capability.
.cursor-plugin/plugin.json Adds Cursor plugin metadata, but does not declare the Skill capability used by the generated Codex manifest.
plugin.json Adds the root plugin manifest with metadata matching the source Claude manifest.
hooks.json Adds a root hook manifest with a cwd-relative Node command for the WebFetch hint hook.
release-please-config.json Adds the new version-bearing manifests to release-please extra-files.

Fix All in Claude Code

Prompt To Fix All With AI
Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
hooks.json:10
**Hook Path Depends On Cwd**

When the hook runner starts commands from a user's workspace instead of the installed plugin root, `node "./hooks/fetch-hint.mjs"` resolves against that workspace. Node then cannot find the plugin's `hooks/fetch-hint.mjs`, so the WebFetch PreToolUse hint hook fails before the script can run.

### Issue 2 of 2
.cursor-plugin/plugin.json:5
**Cursor Manifest Lacks Capability Metadata**

The Cursor manifest only carries display metadata, while the Codex manifest declares the plugin capability as `Skill`. If Cursor's loader uses manifest-declared capabilities to register provided skills, this file can load as a metadata-only plugin and leave Ask's skills unavailable in Cursor.

Reviews (1): Last reviewed commit: "chore: generate Codex, Cursor, and Antig..." | Re-trigger Greptile

Comment thread hooks.json
Comment thread .cursor-plugin/plugin.json
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying ask with  Cloudflare Pages  Cloudflare Pages

Latest commit: 60091a1
Status: ✅  Deploy successful!
Preview URL: https://28bbb0a6.ask-6im.pages.dev
Branch Preview URL: https://chore-multi-runtime-plugin-m.ask-6im.pages.dev

View logs

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 5 files

Architecture diagram
sequenceDiagram
    participant SOT as Source of Truth (.claude-plugin/plugin.json)
    participant Gen as Multi-Format Generator
    participant CP as Codex Plugin (.codex-plugin/plugin.json)
    participant CursorP as Cursor Plugin (.cursor-plugin/plugin.json)
    participant AGP as Antigravity Plugin (plugin.json)
    participant AGH as Antigravity Hooks (hooks.json)
    participant RP as Release Please Config (release-please-config.json)
    participant Client as Agent Client (Codex/Cursor/Antigravity)

    Note over SOT,RP: Manifest Generation Flow

    SOT->>Gen: read plugin metadata (name, version, description, author, etc.)
    Gen->>Gen: transform to Codex format (interface.displayName, category, etc.)
    Gen->>CP: write .codex-plugin/plugin.json
    Gen->>Gen: transform to Cursor format (displayName, tags, etc.)
    Gen->>CursorP: write .cursor-plugin/plugin.json
    Gen->>Gen: transform to Antigravity root format (no interface block)
    Gen->>AGP: write plugin.json
    Gen->>Gen: rewrite path references (${CLAUDE_PLUGIN_ROOT}/ → ./)
    Gen->>AGH: write hooks.json (mirror of hooks/hooks.json with rewritten paths)
    Gen->>RP: register extra-files entries for version syncing

    Note over CP,AGP: Runtime Loading Flow

    Client->>CP: load manifest (Codex runtime)
    Client->>CursorP: load manifest (Cursor runtime)
    Client->>AGP: load manifest (Antigravity runtime)
    Client->>AGH: load hooks (Antigravity runtime)

    alt Version Update Triggered
        RP->>RP: on release, bump $.version in all manifests
        RP->>CP: sync version to 0.4.11
        RP->>CursorP: sync version to 0.4.11
        RP->>AGP: sync version to 0.4.11
    end

    Note over Client: Plugin loaded with capabilities metadata
    Client->>Client: initialize plugin based on manifest
Loading

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread hooks.json
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying ask-registry with  Cloudflare Pages  Cloudflare Pages

Latest commit: 60091a1
Status: ✅  Deploy successful!
Preview URL: https://d7a7f4ad.ask-registry.pages.dev
Branch Preview URL: https://chore-multi-runtime-plugin-m.ask-registry.pages.dev

View logs

@amondnet amondnet merged commit eb0ad74 into main Jul 8, 2026
13 checks passed
@amondnet amondnet deleted the chore/multi-runtime-plugin-manifests branch July 8, 2026 01:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files. type:chore Maintenance, build, dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant