feat: use --name as repository domain in repo create and init

[jomifepe]

Summary

• prismic repo create --name now sets the repository domain (URL slug), not just the display label. Previously the domain was a random 8-char hex string regardless of --name.
• Adds --display-name (-d) on repo create to control the human-readable label separately, matching the dashboard's two-field model.
• --name is required on repo create and validated against the same rule API uses: 4–63 chars, ^[a-zA-Z0-9][-a-zA-Z0-9]{2,}[a-zA-Z0-9]$. Invalid input errors with guidance. Valid input is lowercased before submitting (API lowercases server-side).
• prismic init --repo <name> now creates the repository if it doesn't already exist in your account (and is available). If the name is taken by another account, it errors clearly.

How to QA [^1]

• npx prismic@pr-180 repo create --name my-test-repo → Creates a repo at my-test-repo
• npx prismic@pr-180 repo create --name foo-bar --display-name "Foo Bar" → Sets domain foo-bar and label Foo Bar in the dashboard
• npx prismic@pr-180 repo create --name "My Test Repo" → Errors with validation guidance (spaces are not allowed)
• npx prismic@pr-180 repo create --name "!!" → Errors with validation guidance
• npx prismic@pr-180 init --repo my-new-repo in a fresh project → Creates my-new-repo and writes it to prismic.config.json
• npx prismic@pr-180 init --repo prismic → Errors (name taken by another account)
• npx prismic@pr-180 init → Errors asking for --repo

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes repository creation/selection flow in prismic init and prismic repo create, which can affect onboarding behavior and error handling when creating or attaching to repos. Risk is moderate due to new validation and availability checks against remote services.

Overview
prismic repo create now requires --name and uses it as the repository domain (lowercased), with a new --display-name to set the human-readable label separately; it validates names via a shared repositoryNameSchema and fails early if the domain is unavailable.

prismic init now requires --repo, lowercases it, and will create the repository automatically when the user doesn’t already have access (after validating the name and checking domain availability); it only enforces Type Builder being enabled when connecting to an existing accessible repo. The command framework adds optional per-option Zod schema validation, and tests are updated to cover the new required/validation behaviors and repo cleanup.

^{Reviewed by Cursor Bugbot for commit b163f83. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b163f83. Configure here.}

[cursor]

Redundant domain availability check in init flow

Low Severity

When init creates a new repo, checkIsDomainAvailable is called at init.ts line 115, then createRepo at line 131 calls it a second time internally at repo-create.ts line 60. This is a redundant HTTP request on every init --repo <new-name> run. The first check provides a contextual error message, and the second is a general safety check inside createRepo — but both hit the same API endpoint with the same arguments, with getAdapter() running in between.

Additional Locations (1)

• src/commands/repo-create.ts#L59-L64

 

^{Reviewed by Cursor Bugbot for commit b163f83. Configure here.}