cyberneticlibrary
← library

Sync tool versions across projects

sync-templatecommandsetup L2★0
motlin/motlin-chess ↗
What it does

Sync tool versions from TypeScript template to sibling projects

Best for

Organizations managing multiple TypeScript projects where configuration drift causes CI/lint/format inconsistencies.

Inputs
  • · Sibling project name or 'all' (list from .llm/sync-projects.md)
  • · Template project as source of truth
Outputs
  • · Task list per sibling (.llm/todo.md replacement)
  • · Identified version mismatches (Mise, npm, pnpm, GitHub Actions, linters)
  • · Prerequisite tracking (Vite+ migration, pre-commit setup)
Requires
  • · git
  • · npm (version checks)
  • · Mise
  • · GitHub API (for release versions)
Preconditions
  • · .llm/sync-projects.md exists (machine-specific, gitignored)
  • · Template project has current versions
  • · Sibling projects have .mise/config.toml, package.json, GitHub workflows
Failure modes
  • · Template outdated — user must update template first (checked in Step 1)
  • · Sibling newer than template — user must decide: pull or keep custom version
  • · .llm/sync-projects.md missing — ask user to create it
Trust signals
  • · 3-step workflow (update template, pull improvements from siblings, push to all)
  • · Prerequisite tracking (Vite+ migration blocks subsequent tasks)
  • · Source attribution on every task (links back to template)