Skip to content

feat: add elizaos-plugin-omnifun#296

Open
0xzcov wants to merge 1 commit intoelizaos-plugins:mainfrom
0xzcov:add-elizaos-plugin-omnifun
Open

feat: add elizaos-plugin-omnifun#296
0xzcov wants to merge 1 commit intoelizaos-plugins:mainfrom
0xzcov:add-elizaos-plugin-omnifun

Conversation

@0xzcov
Copy link

@0xzcov 0xzcov commented Mar 15, 2026

Summary

Adds elizaos-plugin-omnifun — multichain memecoin launchpad plugin for ElizaOS.

Tokenize your AI agent as an oMeme and earn passive USDC forever across EVM and non-EVM chains simultaneously — from a single LP. 0.5% creator fee + 50% Uniswap V3 LP fees after graduation. 8 chains, 5-25s settlement.

8 actions: register, trade, launch, portfolio, feed, quote, rewards, strategy

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features
    • New elizaos-plugin-omnifun plugin is now available for integration.

Greptile Summary

Adds elizaos-plugin-omnifun to the plugin registry — a multichain memecoin launchpad plugin for ElizaOS by 0xzcov.

  • The change is a single-line addition to index.json, which is the expected format for registry submissions
  • The entry is correctly alphabetically sorted among unscoped packages (after all @-scoped packages)
  • JSON formatting is valid with proper comma placement
  • The npm package name (elizaos-plugin-omnifun) matches the GitHub repo name convention

Confidence Score: 4/5

  • This PR is a minimal, low-risk registry entry addition that follows established conventions.
  • Single-line addition to the plugin registry index. The JSON is valid, alphabetical ordering is correct, and the entry follows the same format as existing entries. No code logic changes involved — this is purely a data/configuration change.
  • No files require special attention. The only change is a single line in index.json.

Important Files Changed

Filename Overview
index.json Adds a single new registry entry for elizaos-plugin-omnifun pointing to github:0xzcov/elizaos-plugin-omnifun. The entry is correctly placed in alphabetical order, uses valid JSON formatting, and follows the existing "package-name": "github:org/repo" convention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: Add elizaos-plugin-omnifun] --> B[index.json updated]
    B --> C[GitHub Action triggered on merge]
    C --> D[Process plugin entry]
    D --> E[Fetch metadata from github:0xzcov/elizaos-plugin-omnifun]
    E --> F[Update generated-registry.json]
    F --> G[Plugin available in elizaOS CLI & web registry]
Loading

Last reviewed commit: 425cb5d

(2/5) Greptile learns from your feedback when you react with thumbs up/down!

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 15, 2026

Walkthrough

A new plugin mapping entry for "elizaos-plugin-omnifun" is added to index.json, pointing to the GitHub repository "0xzcov/elizaos-plugin-omnifun" and positioned alphabetically among other elizaos-prefixed plugins.

Changes

Cohort / File(s) Summary
Plugin Registry
index.json
Adds a new plugin mapping entry "elizaos-plugin-omnifun": "github:0xzcov/elizaos-plugin-omnifun" to the plugins configuration map.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A new plugin hops into the fold,
With GitHub's path, a story told—
Omnifun awaits to bring its cheer,
The registry's grown throughout the year! 🐰✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning PR description provides plugin details but omits required Registry Update Checklist items needed to verify compliance with repository standards. Add the Registry Update Checklist to verify: JSON formatting, alphabetical ordering, GitHub repo accessibility, default branch, required topics, README, images, and package.json agentConfig compliance.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: adding a new plugin entry to the registry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

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 and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant