Template Asset Management
Templates are one repoctl capability. @icebreakers/monorepo-templates packages built-in project templates and managed repository assets; templates under templates/* are private source workspaces and are not published independently.
Built-In Mapping
Template metadata defines a stable key, category, source directory, default target, and description. The CLI, create commands, and documentation consume the same registry.
repo templates
repo templates tsdown
repo templates --category libraryCreation Plans
repo new sdk --template tsdown --dry-run
repo new docs --template vitepress --json --out plans/docs.jsonA plan records the selected template, source, destination, package name, workspace pattern, and whether fallback behavior was used. Unknown explicit keys fail with a suggestion.
Health Checks
repo templates --check
repo templates --check --jsonHealth checks validate unique sources and targets, source directories, package manifests, metadata, and filtered temporary files.
Managed Assets
repo init and repo upgrade synchronize root scripts, configuration, hooks, and release assets. Existing custom files are preserved unless overwrite behavior is explicitly selected.
Repository maintainers refresh packaged copies with:
pnpm --filter @icebreakers/monorepo-templates sync:assetsGenerated copies should never be edited by hand.
