| name | pluxx-maintain-plugin |
| description | Use this skill when an existing MCP-derived Pluxx project must be refreshed after its MCP, docs, runtime, or scaffold inputs change. Preview and run sync, preserve custom sections, explain drift, and route semantic changes to refinement. |
Maintain A Pluxx Plugin
Refresh generated source without losing user-owned work.
Workflow
- Confirm that
.pluxx/mcp.json exists and the project is MCP-derived.
- Inspect the working tree. Do not sync across unrelated uncommitted changes without isolating or preserving them.
- Preview first:
pluxx sync --dry-run --json- use
--from-mcp <source> only when the canonical source changed intentionally
- Read references/sync-safety.md before applying sync, or whenever the preview contains removed, preserved, renamed, or warning entries.
- Review added, updated, removed, preserved, renamed, and warning entries before applying.
- Run
pluxx sync after the preview is understood.
- Inspect mixed-ownership Markdown boundaries and any custom notes attached to removed generated surfaces.
- Run
pluxx validate, pluxx doctor, pluxx lint, pluxx eval, and pluxx test; run skills-ref validate for every source skill.
- Route changed product meaning, tool grouping, or setup behavior to
pluxx-refine-plugin.
Drift Rules
- Never delete preserved custom content silently.
- Call out removed MCP tools that strand a workflow or custom note.
- Treat persisted taxonomy and invalidated agent packs as explicit review work, not incidental generated noise.
- Keep source fixes in the root project and rebuild
dist/ through Pluxx.
- Treat a changed local stdio command or payload path as a runtime change that needs install verification.
Output
Report the source used, preview summary, applied changes, preserved content, warnings, validation result, and any refinement or install-proof follow-up.
