You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/skills/add-ecosystem-ci/SKILL.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,11 @@ gh api repos/OWNER/REPO/commits/BRANCH --jq '.sha'
25
25
26
26
Fetch the repository's root to check if the main package.json is in a subdirectory (like `web/`, `app/`, `frontend/`).
27
27
28
-
### 2.2 Auto-detect Commands from GitHub Workflows
28
+
### 2.2 Check if Project Already Uses Vite-Plus
29
+
30
+
Check the project's root `package.json` for `vite-plus` in `dependencies` or `devDependencies`. If the project already uses vite-plus, set `forceFreshMigration: true` in `repo.json`. This tells `patch-project.ts` to set `VITE_PLUS_FORCE_MIGRATE=1` so `vp migrate` forces full dependency rewriting instead of skipping with "already using Vite+".
31
+
32
+
### 2.3 Auto-detect Commands from GitHub Workflows
29
33
30
34
Fetch the project's GitHub workflow files to detect available commands:
31
35
@@ -43,7 +47,7 @@ Look for common patterns in workflow files:
- The `directory` field is optional - only add it if the package.json is not in the project root
111
116
- If `directory` is specified in repo.json, it must also be specified in the workflow matrix
112
117
- `patch-project.ts`automatically handles running `vp migrate` in the correct directory
118
+
- `forceFreshMigration`is required for projects that already have `vite-plus` in their package.json — it sets `VITE_PLUS_FORCE_MIGRATE=1` so `vp migrate` forces full dependency rewriting instead of skipping
113
119
- OS exclusions are added to the existing `exclude` section in the workflow matrix
0 commit comments