new-repo

new-repo — scaffold a RepoKit-standard repository

You scaffold a new repository by copying bundled templates and filling in their {{placeholders}} (copy-and-fill — there is no separate templating engine). You stop at local review: you may create a private GitHub repo on request, but you never push to a public remote and never publish.

Your templates live under this skill's own directory. At load you were given a line Base directory for this skill: <ABS>. Read every template as <ABS>/templates/<...>. Do not rely on ${CLAUDE_PLUGIN_ROOT} or a bare relative path — use the absolute base path you were given.

Two reference files (read them from the same base dir as you need them):

• references/file-set-resolution.md — exactly which templates apply for a given type × tier.
• references/placeholders.md — the placeholder list and the post-scaffold self-check.

Inputs

Gather these from the user's arguments / message, else ask — keep it to load-bearing questions:

• name — the repo / directory name. Default kebab-case; a deliberate branding name (a camelCase product name, say) is a legitimate user choice, not a mistake — accept it without argument and record it in ADR-0001 (see the standard's Naming conventions).
• description — one line.
• type — one of: powershell-module, docker-compose, power-platform-connectors, skill-plugin, collection, mcp-server, app-ts, app-python, script-collection.
• visibility — private (= Core tier), public (= +Public), or published (= +Published).
• author — the identity stamped wherever an author/owner/copyright value is written. Default: the GitHub handle of the gh-authenticated user (gh api user --jq .login; no gh → ask). A real personal name only when the user explicitly chooses one for this repo — that choice is a declared variance: record it in ADR-0001 and give it a START-HERE row (see the standard's Author identity).
• license — default Apache-2.0.
• living-docs add-on — yes/no, default no. Ask: "Will this repo's docs track live operational state (deployed resources, scheduled jobs, long-running migrations)?" If yes, the add-on stamps docs/RUNBOOK.md, docs/STATE.json, scripts/check-docs.ps1, and a docs.yml check workflow (see references/living-docs-rules.md).
• early licence — private repos only, default no. Ask: "Is a public release already planned?" If yes, stamp LICENSE now from the Public-tier template, and ask one follow-up: "Will third-party licensed material be incorporated while still private?" — if so, also stamp NOTICE (see references/file-set-resolution.md, Early licence). Record both answers in ADR-0001. No START-HERE variance row — an early licence on a promotion-planned repo follows the standard's Promotion path, it doesn't deviate from it.
• For powershell-module only: ModuleName (PascalCase, e.g. MyModule).