plugin-manager

Reviews, merges, promotes, and rolls back skill changes for the lia-plugins marketplace.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill plugin-manager-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-manager
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/plugin-manager
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill plugin-manager-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a Claude Code plugin marketplace involves error-prone operational work: reviewing skill PRs, landing merges correctly, promoting releases to machines, rolling back bad builds, and keeping versions, frontmatter, and documentation truthful. This Skill encodes that operational discipline so the marketplace is run consistently rather than re-derived each session. ## Core Features & Use Cases - Skill change review and landing: Runs the review-and-merge loop with content-verified squash merges, one ticket per PR, and a strict rule that a session never lands its own work. - Promotion and rollback: Executes the deliberate promotion of merges to the release ref and force-move rollback of bad builds, with verification that a real install received the change. - Roster and version hygiene: Enforces frontmatter checks, semver bump discipline (patch/minor/major as claims about the change), pin management, and keeps MANUAL.md accurate in the same PR as any change. - Use Case: A skill PR lands on main and needs to reach every team machine. This seat runs the promotion one-liner, adds the changelog row to MANUAL.md, and verifies a real install pulled the new version before declaring it shipped. ## Quick Start Ask the agent to review and land this skill PR, then promote lia-tools to release and verify the install.

Frequently Asked Questions about plugin-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I promote a merged skill change to all machines?▼

Run the promotion one-liner documented in the repo README's publish section, which moves the release ref to the landed state. Then verify a real install pulled the new version, since auto-update does not deliver on CLI or desktop machines.

How do I roll back a bad plugin release?▼

Rollback is a force-move of the release ref back to the previous good state, which is the one ref where force-push is legitimate. The downgrade delivers because the version changes, and the fix then lands forward through a normal PR.

Why didn't my plugin update after a promotion?▼

Auto-update does not fire on CLI or desktop machines because DISABLE_AUTOUPDATER=1 is set in the session environment. Updates must be pulled by hand with the plugin update command; only cloud and web sessions provision fresh automatically.

What version bump should a skill change get?▼

Take the smallest bump that is true: patch for improvements, minor for new capabilities, major for breaking changes, moving exactly one step. A number is not yours until it lands, since two branches can pick the same version and merge without conflict.

Can a session merge its own skill PR?▼

No. A session never lands its own work, and a self-review does not satisfy the rule. The only exception is the declared path in the review-and-merge protocol, and the merge rules apply to the marketplace repo exactly as to product repos.