fix(config): skip git-hook prompt when staged config already exists

When a user clones a project with staged config in vite.config.ts and
manually runs `vp config`, the prompt was incorrectly shown because
hook shims don't exist after clone (they're gitignored). The existing
staged config is sufficient signal that the project opted into hooks.

Add `hasStagedConfigInViteConfig(root)` check to the prompt condition
so projects with staged config auto-install hooks without prompting.

Closes #1154

Author: fengmk2

packages/cli/snap-tests-global/command-config-auto-hooks/package.json

@@ -0,0 +1,3 @@
+{
+  "name": "command-config-auto-hooks"
+}

packages/cli/snap-tests-global/command-config-auto-hooks/snap.txt

@@ -0,0 +1,17 @@
+> git init
+> vp config # should install hooks automatically without prompting (staged config exists)
+> git config --local core.hooksPath # should be .vite-hooks/_
+.vite-hooks/_
+
+> cat .vite-hooks/pre-commit # should have vp staged
+vp staged
+
+> cat vite.config.ts # should remain unchanged
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  staged: {
+    "*": "vp check --fix"
+  },
+
+});

packages/cli/snap-tests-global/command-config-auto-hooks/steps.json

@@ -0,0 +1,9 @@
+{
+  "commands": [
+    { "command": "git init", "ignoreOutput": true },
+    "vp config # should install hooks automatically without prompting (staged config exists)",
+    "git config --local core.hooksPath # should be .vite-hooks/_",
+    "cat .vite-hooks/pre-commit # should have vp staged",
+    "cat vite.config.ts # should remain unchanged"
+  ]
+}

packages/cli/snap-tests-global/command-config-auto-hooks/vite.config.ts

@@ -0,0 +1,7 @@
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  staged: {
+    '*': 'vp check --fix',
+  },
+});

packages/cli/src/config/bin.ts

@@ -10,7 +10,7 @@ import { join } from 'node:path';
 import mri from 'mri';
 
 import { vitePlusHeader } from '../../binding/index.js';
-import { ensurePreCommitHook } from '../migration/migrator.js';
+import { ensurePreCommitHook, hasStagedConfigInViteConfig } from '../migration/migrator.js';
 import { updateExistingAgentInstructions } from '../utils/agent.js';
 import { renderCliDoc } from '../utils/help.js';
 import { defaultInteractive, promptGitHooks } from '../utils/prompts.js';
@@ -62,9 +62,16 @@ async function main() {
   const isFirstHooksRun = !existsSync(join(root, hooksDir, '_', 'pre-commit'));
 
   let shouldSetupHooks = true;
-  if (interactive && isFirstHooksRun && !dir && !isPrepareScript) {
+  if (
+    interactive &&
+    isFirstHooksRun &&
+    !dir &&
+    !isPrepareScript &&
+    !hasStagedConfigInViteConfig(root)
+  ) {
     // --hooks-dir implies agreement; only prompt when using default dir on first run
     // prepare script implies the project opted into hooks — install automatically
+    // existing staged config in vite.config.ts implies the project already opted in
     shouldSetupHooks = await promptGitHooks({ interactive });
   }
 

rfcs/config-and-staged-commands.md

@@ -282,6 +282,48 @@ Husky <9.0.0 is not supported by auto migration — `vp migrate` detects unsuppo
 | **`vp config`**  | **Reinstall hook shims + agent setup** | **npm `prepare` lifecycle** |
 | **`vp staged`**  | **Run staged linters on staged files** | **Pre-commit hook**         |
 
+## `vp config` Hooks Setup Flow
+
+```
+vp config
+│
+├─ VITE_GIT_HOOKS=0 or HUSKY=0? ──→ Skip hooks (exit 0)
+│
+├─ Not inside a git repo? ──→ Skip hooks (exit 0)
+│
+├─ Should prompt user?
+│   Prompt ONLY when ALL of these are true:
+│   • Interactive terminal (not CI, not piped)
+│   • First run (hook shims don't exist yet)
+│   • No --hooks-dir flag
+│   • Not running from prepare lifecycle
+│   • No staged config in vite.config.ts          ← NEW (#1154)
+│
+│   YES → Prompt "Set up pre-commit hooks?"
+│          User declines → skip hooks
+│   NO  → Auto-install hooks
+│
+├─ core.hooksPath already set to a custom path?
+│   (not .vite-hooks/_, not .husky)
+│   └─ YES → Skip hooks, preserve custom config
+│
+├─ Set core.hooksPath → .vite-hooks/_
+├─ Create hook shims in .vite-hooks/_/
+├─ Ensure staged config in vite.config.ts
+└─ Ensure .vite-hooks/pre-commit contains "vp staged"
+```
+
+### When does the prompt appear?
+
+| Caller                                | Prompts? | Why                                              |
+| ------------------------------------- | -------- | ------------------------------------------------ |
+| `npm install` → prepare               | No       | prepare lifecycle = auto-install                 |
+| Manual, project has `staged` config   | No       | staged config = already opted in **(#1154 fix)** |
+| Manual, no `staged` config, first run | **Yes**  | No signal that project wants hooks               |
+| Manual, already ran before            | No       | Hook shims exist = not first run                 |
+| CI / non-interactive                  | No       | Non-interactive = auto-install                   |
+| `--hooks-dir` flag                    | No       | Explicit flag = intent to install                |
+
 ## Comparison with Other Tools
 
 | Tool                      | Approach                                   |