How this command is triggered — by the user, by Claude, or both
Slash command
/mason-lsp:syncThe summary Claude sees in its command listing — used to decide when to auto-load this command
Run the mason-lsp-sync script to regenerate LSP configuration from Mason.
1. Run the sync script: `${CLAUDE_PLUGIN_ROOT}/mason-lsp-sync`
2. Show the summary output
3. Tell the user to run `/reload-plugins` to apply changesRun the mason-lsp-sync script to regenerate LSP configuration from Mason.
${CLAUDE_PLUGIN_ROOT}/mason-lsp-sync/reload-plugins to apply changesnpx claudepluginhub orestesk/claude-plugins --plugin mason-lsp/syncDisplays deprecation notice that sync is a no-op and recommends Dolt commands: bd dolt push, pull, commit, show for manual synchronization.
/syncSynchronizes task status with git commits by analyzing history, patterns, and references for discrepancies, updating bidirectionally. Supports --check and --date/--project options.
/syncSynchronizes task status with git commits by analyzing history, patterns, and references for discrepancies, updating bidirectionally. Supports --check and --date/--project options.
/syncPulls latest git changes from main (skippable via --no-pull) and syncs docs like prompt_plan.md, spec.md, CLAUDE.md, rules/ with code diffs. Use --check-only to preview.
/syncTriggers plan-sync for task <id> to update downstream task specs after implementation drift. Supports optional --dry-run flag.
/syncRebuilds project_truth.md, orchestrator_state.md, and execution_context.md from all state files and user-confirmed progress, then writes them back.