forge

Your personal template library. Each template is its own private GitHub repository under Dev/Templates/<name>/, flagged as a GitHub template repository.

forge new NAME "DESCRIPTION"

Scaffold a blank template, create its private repo, and register it.

requires gh

Also runs gh repo edit --template, so the repo carries the "Template repository" flag and you can spin new projects off it from GitHub directly. From there you edit and git push like any repo.

$ forge new archon "archicad addons template"

forge list

Numbered list with descriptions and local/remote status.

The number is display-only. Always refer to a template by name — positions shift as you add and remove templates.

$ forge list

forge get NAME|all

Clone registered templates back onto this machine.

$ forge get all
$ forge get archon

forge remove NAME

Delete the local copy. The GitHub repo and registry entry are kept.

$ forge remove archon

forge help

List every command.

$ forge help

Output of forge list

Templates:
  1. archon           archicad addons template         (local + repo)
  2. cli-starter      (no description)                 (repo only (forge get))

Status	Meaning
local + repo	Present in Dev/Templates/ and registered
repo only (forge get)	Registered but not on this machine yet

Names, not numbers

The list number is display-only and shifts as templates are added or removed. Every command takes a name.

Relationship to polyforge create

forge is for your own curated skeletons. The quick built-in starters used by polyforge create are separate and are not managed here.

See also

• Template library guide
• Registry reference