feat: add @guanxing1/plugin-elizaos — Chinese metaphysics AI plugin

[doggychip]

Plugin: @guanxing1/plugin-elizaos (GuanXing 观星)

Overview

GuanXing (观星) is a Chinese metaphysics AI plugin that brings traditional Eastern wisdom to ElizaOS agents. 10 actions covering BaZi (八字), Feng Shui, Tarot, I-Ching, fortune telling, dream interpretation, and more.

Plugin Info

• npm: @guanxing1/plugin-elizaos
• GitHub: doggychip/plugin-guanxing
• Demo: heartai.zeabur.app

Actions (10)

Action	Description
BAZI_ANALYSIS	八字 birth chart analysis
DAILY_FORTUNE	Personalized daily fortune
QIUQIAN	Temple-style divination (求签)
TAROT_READING	Tarot with Eastern interpretation
DREAM_INTERPRETATION	Dream analysis (解梦)
ALMANAC_LOOKUP	Chinese almanac
FENGSHUI_ANALYSIS	Feng Shui analysis
NAME_SCORE	Name scoring (姓名打分)
COMPATIBILITY_CHECK	Compatibility via 八字合盘
ZODIAC_FORTUNE	Chinese zodiac (生肖运势)

Demo Evidence

• Live: https://heartai.zeabur.app
• Also on ClawHub: clawhub install guanxing
• MCP server: @guanxing1/mcp-server on npm

Quality Checklist

• Standard plugin structure (src/, dist/, images/)
• Branding assets (logo.jpg 400x400, banner.jpg 1280x640)
• README complete
• agentConfig in package.json
• Published on npm
• TypeScript, builds clean

Summary by CodeRabbit

Release Notes

• New Features
  • New plugin now available for extending application functionality and capabilities.

Greptile Summary

This PR registers the @guanxing1/plugin-elizaos (GuanXing 观星) Chinese metaphysics AI plugin into the elizaOS plugin registry by adding a single mapping line to index.json. The plugin covers 10 actions including BaZi analysis, Feng Shui, Tarot, I-Ching, dream interpretation, and more.

Changes:

• Adds "@guanxing1/plugin-elizaos": "github:doggychip/plugin-guanxing" to index.json
• Entry is correctly alphabetically sorted between @esscrypt/plugin-polkadot and @kamiyo/eliza
• JSON syntax, github: prefix (not github.com), and absence of a .git extension are all correct

Observations:

• The npm package scope (@guanxing1) and the GitHub repository owner (doggychip) are different identities. While not prohibited by the registry format, this inconsistency makes ownership verification harder and differs from the pattern used by virtually all other third-party entries in the file. The PR description does not explain or reconcile this discrepancy.
• The PR description claims the plugin is published on npm and provides a live demo URL, but no independent verification of the npm package or GitHub repository accessibility was provided within the PR itself.

Confidence Score: 3/5

• Safe to merge after confirming that the npm scope @guanxing1 and the GitHub user doggychip belong to the same author.
• The registry entry is syntactically correct, alphabetically placed, and follows all formatting rules. The only concern preventing a higher score is the unexplained divergence between the npm scope (@guanxing1) and the GitHub username (doggychip), which makes it non-trivial for maintainers to verify that the submitter legitimately controls both endpoints. Once that ownership link is clarified, this is a low-risk, single-line registry addition.
• index.json — verify that the npm scope @guanxing1 and GitHub user doggychip are controlled by the same author before merging.

Important Files Changed

Filename	Overview
index.json	Adds a single registry entry mapping the npm package @guanxing1/plugin-elizaos to github:doggychip/plugin-guanxing; JSON format, alphabetical ordering, and github: prefix are all correct. Minor concern: the npm scope (@guanxing1) and GitHub username (doggychip) are different identities, making ownership harder to verify at a glance.

Sequence Diagram

sequenceDiagram
    participant User
    participant CLI as ElizaOS CLI
    participant Registry as Registry index.json
    participant GH as GitHub doggychip/plugin-guanxing
    participant NPM as npm @guanxing1/plugin-elizaos

    User->>CLI: elizaos plugins install @guanxing1/plugin-elizaos
    CLI->>Registry: Lookup @guanxing1/plugin-elizaos
    Registry-->>CLI: github:doggychip/plugin-guanxing
    CLI->>GH: Fetch plugin source and package.json
    GH-->>CLI: Plugin code plus agentConfig metadata
    CLI->>NPM: Optionally resolve published package
    NPM-->>CLI: Published package artifacts
    CLI-->>User: Plugin installed and ready

Loading

_{Last reviewed commit: "feat: add @guanxing1..."}

Greptile also left 1 inline comment on this PR.

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

[coderabbitai]

Walkthrough

A new plugin mapping entry for @guanxing1/plugin-elizaos pointing to github:doggychip/plugin-guanxing has been added to the plugin registry configuration file. This introduces a single public plugin reference without modifying existing entries.

Changes

Cohort / File(s)	Summary
Plugin Registry Update index.json	Added plugin mapping entry @guanxing1/plugin-elizaos: github:doggychip/plugin-guanxing to register new public plugin.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A new plugin hops into place,
Simple, swift, with effortless grace,
One line added to the registry bright,
Another tool ready to take flight! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description is comprehensive and well-structured, covering plugin overview, actions, demo evidence, and a quality checklist. However, it does not explicitly address all required registry checklist items from the template.	Explicitly verify and confirm in the PR description: (1) that the npm scope @guanxing1 and GitHub user doggychip are controlled by the same author, (2) that all Registry Update Checklist items have been completed, and (3) that the new plugin repo meets all specified requirements (public accessibility, main branch, topics, structure, images, agentConfig format).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: adding the GuanXing Chinese metaphysics AI plugin to the registry, matching the single-line addition in index.json.
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

📝 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Mismatched npm scope and GitHub username

The npm package is scoped under @guanxing1 while the GitHub repository is owned by doggychip. Every other third-party entry in this registry uses the same organisation or username on both sides (e.g. "@erdgecrawl/plugin-base-signals": "github:erdGeclaw/plugin-base-signals" shares the same identity). Having two completely different identifiers here makes it difficult for maintainers to verify that the submitter controls both the npm scope and the GitHub repository, and can create confusion for users who try to trace the package back to its source.

If doggychip is the GitHub identity for the @guanxing1 npm org, please add a brief note to the PR confirming this relationship (e.g. by linking the npm user profile or the organisation's GitHub settings page). If a dedicated GitHub organisation matching the npm scope exists, consider hosting the repository there instead.