tui-write-migration

Where to find the previous major version's source

Use whichever approach is available:

• GitHub MCP (if installed) — browse the repo directly via MCP tools, targeting the v{N-1}.x branch
• git show — browse any file from the previous major branch without a separate checkout: git show v{N-1}.x:projects/<package>/index.ts
• Scripts in the scripts/ directory alongside this skill — resolve the correct branch from package.json automatically:
  • browse-exports.sh <path> — fetch a file via gh CLI
  • search-symbol.sh <EntityName> — find which package exported a symbol

Coverage triage: which entities are worth migrating

You can't directly tell which removed entities real projects depend on. Documentation presence is the proxy for usage: anything Taiga advertised through its own demo/docs is the non-negotiable milestone — cover it ~100%. Entities that were never documented are far more likely to be unused (or used only by someone digging through internals) and can wait.

Work from a list of names that exist in v{N-1}.x but not in main — just names. Do not pull replacement details until a name clears triage; that keeps context clean.

For each name, decide coverage by demo presence, searching twice: