feat: add /add-ecosystem-ci skill for adding test cases

Replace CLAUDE.md documentation with an interactive skill that guides
through adding new ecosystem-ci test cases. The skill prompts for
repository URL, directory, node version, and commands to run.

Author: fengmk2

.claude/commands/add-ecosystem-ci.md

@@ -0,0 +1,64 @@
+---
+description: Add a new ecosystem-ci test case for testing real-world projects against vite-plus
+allowed-tools: Bash, Read, Edit, Write, WebFetch, AskUserQuestion
+---
+
+# Add Ecosystem-CI Test Case
+
+Add a new ecosystem-ci test case following this process:
+
+## Step 1: Get Repository Information
+
+Ask the user for the GitHub repository URL if not provided as argument: $ARGUMENTS
+
+Use GitHub CLI to get repository info:
+```bash
+gh api repos/OWNER/REPO --jq '.default_branch'
+gh api repos/OWNER/REPO/commits/BRANCH --jq '.sha'
+```
+
+## Step 2: Check for Subdirectory
+
+Fetch the repository's root to check if the main package.json is in a subdirectory (like `web/`, `app/`, `frontend/`).
+
+Ask the user:
+- Which directory contains the main package.json? (root or subdirectory)
+- What Node.js version to use? (22 or 24)
+- Which commands to run? (e.g., lint, build, test, type-check)
+
+## Step 3: Update Files
+
+1. **Add to `ecosystem-ci/repo.json`**:
+   ```json
+   {
+     "project-name": {
+       "repository": "https://github.com/owner/repo.git",
+       "branch": "main",
+       "hash": "full-commit-sha",
+       "directory": "web"  // only if subdirectory is needed
+     }
+   }
+   ```
+
+2. **Add to `.github/workflows/e2e-test.yml`** matrix:
+   ```yaml
+   - name: project-name
+     node-version: 24
+     directory: web  # only if subdirectory is needed
+     command: |
+       vite run lint
+       vite run build
+   ```
+
+## Step 4: Verify
+
+Test the clone locally:
+```bash
+pnpm dlx tsx ecosystem-ci/clone.ts project-name
+```
+
+## Important Notes
+
+- The `directory` field is optional - only add it if the package.json is not in the project root
+- If `directory` is specified in repo.json, it must also be specified in the workflow matrix
+- `patch-project.ts` automatically handles running `vite migrate` in the correct directory

CLAUDE.md

@@ -106,56 +106,3 @@ pnpm -F vite-plus-cli snap-test migration-skip-vite-peer-dependency
 ```
 
 The snap test will automatically generate/update the `snap.txt` file with the command outputs. It exits with zero status even if there are output differences; you need to manually check the diffs(`git diff`) to verify correctness.
-
-## Ecosystem-CI Tests
-
-Ecosystem-CI tests real-world projects against vite-plus. Located in `ecosystem-ci/`.
-
-### Adding a New Test Case
-
-1. **Get repository info** using GitHub CLI:
-   ```bash
-   gh api repos/OWNER/REPO --jq '.default_branch'
-   gh api repos/OWNER/REPO/commits/BRANCH --jq '.sha'
-   ```
-
-2. **Add entry to `ecosystem-ci/repo.json`**:
-   ```json
-   {
-     "project-name": {
-       "repository": "https://github.com/owner/repo.git",
-       "branch": "main",
-       "hash": "full-commit-sha",
-       "directory": "web"  // optional: subdirectory containing package.json
-     }
-   }
-   ```
-
-3. **Add test matrix entry to `.github/workflows/e2e-test.yml`**:
-   ```yaml
-   - name: project-name
-     node-version: 24
-     directory: web  # optional: must match repo.json if specified
-     command: |
-       vite run lint
-       vite run build
-   ```
-
-4. **Test locally**:
-   ```bash
-   pnpm dlx tsx ecosystem-ci/clone.ts project-name
-   ```
-
-### Key Files
-
-- `ecosystem-ci/repo.json` - Project definitions (repository, branch, hash, optional directory)
-- `ecosystem-ci/clone.ts` - Clones projects to temp directory
-- `ecosystem-ci/patch-project.ts` - Runs `vite migrate` on cloned projects
-- `.github/workflows/e2e-test.yml` - CI workflow with test matrix
-
-### Subdirectory Support
-
-For projects where the web app is in a subdirectory (e.g., `dify/web`):
-- Add `"directory": "subdir"` to repo.json entry
-- Add `directory: subdir` to workflow matrix entry
-- `patch-project.ts` and workflow steps automatically use the subdirectory