populate-from-template

name	populate-from-template
description	Take a template from the user's license template store and populate its placeholders ({{year}}, {{copyright_holder}}, {{project_name}}, etc.), then write the result as LICENSE (or a user-specified path) in the current project. Use when the user says "add MIT license", "populate the apache template here", or after recommend-license points to an existing template.

Populate From Template

Render a stored template into a concrete LICENSE file.

Steps

1. Read plugin config. Resolve template_store_path. If config missing, invoke setup-template-store.
2. Identify the requested template:
   • If the user named a license (e.g. "MIT"), match against filename and frontmatter name (case-insensitive).
   • If ambiguous or absent, run list-templates first and ask the user to pick.
3. Load the template body. Extract all {{token}} placeholders.
4. Resolve each placeholder:
   • {{year}} → current year (or range if user specifies).
   • {{copyright_holder}} → ask the user; default to git user.name from git config user.name if available.
   • {{project_name}} → infer from current directory basename; confirm with user.
   • Any other tokens → ask the user, batched into a single message.
5. Determine output path:
   • Default: LICENSE in the current working directory.
   • If LICENSE already exists, show a diff and ask before overwriting.
   • Allow override (e.g. LICENSE.md, docs/LICENSE).
6. Write the file. If the project is a git repo, optionally git add LICENSE (do not commit unless asked).
7. Update package.json, pyproject.toml, Cargo.toml, etc. only if the user explicitly asks — do not silently mutate manifests.
8. Report: template used, output path, tokens substituted.

Notes

• Templates are user-owned. Never modify the template files themselves during populate.
• If a token has no obvious resolution and the user does not provide a value, leave it as {{token}} and warn — do not invent values.