Skip to content

goldziher/poly

v0.29.0MIT

Zero-dependency lint & format orchestrator over MCP — one pure-Rust binary wrapping ruff/oxc/taplo/rumdl and more as in-process backends, plus a tree-sitter generic tier for everything else. Exposes lint/format/cache tools with structured JSON output.

GitHubOpen Website

Poly coding-agent plugins

The native ai-rulez authoring sources in .ai-rulez/ generate eleven runtime profiles from five public skills and two prompts. Contributor rules and maintainer agents stay in the repository root and are excluded from this package. Install poly on PATH first: these bundles register poly mcp or teach CLI workflows; they do not install the executable.

Claude Code installs the repository marketplace with /plugin marketplace add Goldziher/poly and /plugin install poly@poly. Codex uses codex plugin marketplace add Goldziher/poly then codex plugin add poly@poly. Both marketplace indexes point to this directory.

For local testing, clone the repository and use the generated files below:

RuntimeEntry point or local installation
Claude Code.claude-plugin/plugin.json
Cursor.cursor-plugin/plugin.json
Codexplugin.json and .codex-plugin/plugin.json
Geminigemini extensions install ./plugin; run from the repository root
Kimikimi.plugin.json; requires the Kimi Python CLI that supports plugins
OpenCodepackage.json exposes .opencode/plugins/poly.js for its v2 API
Factory.factory-plugin/plugin.json
Hermes.hermes/package/pyproject.toml and .hermes/plugins/poly/plugin.yaml
Pipi install ./plugin; run from the repository root
Agent Pluginsplugin.json and mcp.json, spec 1.0
Copilotplugin.json and mcp.json in the shared Agent Plugins layout; prompt commands are not bundled

Pi can also install the Git repository using pi install git:github.com/Goldziher/poly. The private root package manifest points to this directory's native skills and prompts. Pi uses its bash tool to call the installed CLI; it does not register MCP. The release job publishes @goldziher/opencode-poly from this directory, retaining its existing package name. Registry installs obtain these updated resources after the next package release; no current registry version is overwritten by this migration.

For Hermes, install the generated local package with uv pip install --python /path/to/hermes/venv/bin/python ./plugin/.hermes/package from the repository root, then explicitly enable poly in that Hermes installation's config.yaml under plugins.enabled. Skills are opt-in namespace loads, such as poly:poly-mcp; they do not enter the flat system skill listing. The poly_call tool bridges all eleven native MCP tools. Choose list_tools to inspect their request schemas, then pass tool_arguments to the selected tool. Checking workspace lint can compile dependencies; mutating tools (lint_fix, format_write, cache_clean, workspace_lint_fix) modify files or caches and should only be used when the current task authorizes those changes.

Public skills install independently with npx skills add Goldziher/poly --skill poly-mcp. Their source is plugin/.ai-rulez/skills; scripts/sync_public_skills.py --check verifies the repository's skills/ mirror, including resource bytes, namespaces and ownership.

Generation and verification use ai-rulez 5.3.0 based on reviewed source bdabc8a6e9211de60ca1e4ad76225ac92fcf218f. CI pins that source because the initial 5.3.0 release lacks several required plugin fixes. Run task plugin:generate, task plugin:verify and task plugin:test. Native package artifacts and marketplace indexes attach to tagged releases. The manual plugin artifact workflow packages its selected checkout after checking that the core and plugin versions match an existing release tag. Marketplace indexes pin the checkout's immutable commit, and the verified archive attaches to that release; the workflow does not create a product tag or publish registry packages.