plugins/lisa/skills/plugin-sync-explain/SKILL.md
Read-only diagnostic for Lisa plugin source/generated drift. Compares plugins/src against generated plugins/lisa* status, reports source-not-built, generated-only, and marketplace registration drift, and preserves the working tree.
npx skillsauth add codyswanngt/lisa plugin-sync-explainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
/lisa:plugin-sync-explain explains why the plugin sync gate would need attention without mutating the working tree.
Inspect the current Lisa repository, or an optional path passed as $ARGUMENTS, using scripts/plugin-sync-explain.mjs.
The diagnostic is read-only:
bun run build:plugins.bun run check:plugins..claude-plugin/marketplace.json.Report a concise terminal-first summary with stable classifications:
SOURCE_NOT_BUILT: files under plugins/src/** changed without their generated plugins/lisa* counterpart.GENERATED_ONLY: files under plugins/lisa* changed without their plugins/src/** source counterpart.MARKETPLACE_REGISTRATION_DRIFT: a built plugin directory is missing from .claude-plugin/marketplace.json, or a marketplace source points at a missing built directory.OUT_OF_SYNC: source and generated counterparts both changed and need human review.IN_SYNC: no plugin source/generated or marketplace registration drift was detected.For every finding, include the evidence path and the smallest source-first next action. Prefer bun run build:plugins only after source edits are in the right place, and preserve bun run check:plugins as the final reproducibility gate.
$ARGUMENTS or the current directory.git status --porcelain before the diagnostic.node plugins/lisa/scripts/plugin-sync-explain.mjs "$REPO_PATH"
If running from the source tree before generated artifacts are rebuilt, use:
node plugins/src/base/scripts/plugin-sync-explain.mjs "$REPO_PATH"
git status --porcelain after the diagnostic and confirm it is unchanged.scripts/check-plugins-sync.sh; it explains the gate but does not replace it.plugins/src/** as the source of truth and plugins/lisa* as generated artifacts.documentation
Onboard a user to the project via its LLM Wiki. Interviews the user about themselves in relation to the project, captures that to project-scoped memory only, then gives a guided tour of what the project is and sample questions they can ask. Use when someone is new to the project or asks to be onboarded. Read-mostly — it does not open PRs or write PII into the wiki.
documentation
Migrate an existing, hand-rolled wiki implementation onto the lisa-wiki kernel — phased and compatibility-first, with a strict no-loss guarantee. Use when adopting lisa-wiki in a repo that already has its own wiki/, ingest skills, docs, or roles. Renaming things into the canonical shape is fine; losing functionality or data is not. Ends by running /doctor.
development
Health-check the LLM Wiki. Reports orphan pages, contradictions, stale claims, broken internal links, missing index/log coverage, structure-manifest violations, and secret/tenant leaks. Use periodically or before hardening a wiki. Read-only — it reports findings, it does not fix them.
testing
Ingest source material into the LLM Wiki. With an argument (URL, file path, or prompt) it ingests that one source; with no argument it runs a full ingest across every enabled non-external-write source. Routes to the right connector, then runs the ordered pipeline (source note → synthesis → index → log → verify → state → commit/PR). Use whenever new knowledge should enter the wiki.