plugins/lisa-agy/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.development
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
development
Guidelines for upgrading Expo SDK versions and fixing dependency issues
development
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).
tools
`@expo/ui/swift-ui` package lets you use SwiftUI Views and modifiers in your app.