Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/CodySwannGT/lisa --skill lisa-plugin-sync-explainLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
This skill should be used for any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks. It accepts a ticket URL (Jira, Linear, GitHub), a file path containing a spec, or a plain-text prompt. It assembles an agent team, breaks the work into structured tasks, and manages the full lifecycle from research through implementation, code review, deploy, and empirical verification.
any non-trivial request —…
This skill should be used for any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks. It accepts a ticket URL (Jira, Linear, GitHub), a file path containing a spec, or a plain-text prompt. It assembles an agent team, breaks the work into structured tasks, and manages the full lifecycle from research through implementation, code review, deploy, and empirical verification.
Basé sur la classification professionnelle SOC
Affichage de SKILL.md
| name | lisa-plugin-sync-explain |
| description | Read-only diagnostic for Lisa… |
| allowed-tools | ["Bash","Read"] |
/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"
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.