initial commit seems meaningless for custom template

[forehalo]

Describe the bug

I have a fully customized project template, and every time I run vp create <link-to-template>, I will be asked to whether

◇ Initialize a git repository with an initial commit?
  Yes/No

Case 1: Conflict with customized commitlint

The problem is I have my template configured to adapt conventional commits, but the built-int initial commit message is Initial commit from Vite+, which won't fit the rules.

Initial commit failed

⚠ Skipping backup because there’s no initial commit yet. This might result in data loss.

[STARTED] Preparing lint-staged...
[COMPLETED] Preparing lint-staged...
[STARTED] Running tasks for staged files...
[STARTED] Config object — 53 files
[STARTED] * — 53 files
[STARTED] vp check --fix
[COMPLETED] vp check --fix
[COMPLETED] * — 53 files
[COMPLETED] Config object — 53 files
[COMPLETED] Running tasks for staged files...
[STARTED] Applying modifications from tasks...
[COMPLETED] Applying modifications from tasks...
⧗   --- input ---
Initial commit from Vite+
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

VITE+ - commit-msg script failed (code 1)

Case 2: Template placeholders

It's common that template provide something like APP_NAME placeholders that should be replaced to real name after project created. vp create doesn't have it built-in, so the placeholders will go into that initial commit. I have to run sed manually and patch that changes to the initial commit.

Of course I can say "No" for questioning me "Initialize a git repository with an initial commit?", but I will end up running git init manually. It would be good if the question becomes

Initialize a git repository?
Yes/No

Reproduction

https://github.com/yii-labs/vp-monorepo-template

Steps to reproduce

No response

System Info

❯ vp --version
VITE+ - The Unified Toolchain for the Web

vp v0.2.1

Local vite-plus:
  vite-plus  Not found

Tools:
  vite             Not found
  rolldown         Not found
  vitest           Not found
  oxfmt            Not found
  oxlint           Not found
  oxlint-tsgolint  Not found
  tsdown           Not found

Environment:
  Package manager  Not found
  Node.js          v24.18.0

Used Package Manager

pnpm

Logs

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.