vue-ci
Run vue-skills-ci on a Vue or Nuxt project and fix what it reports (TypeScript 7 with vue-tsc, Pinia 4 and Vitest 5 peers, VueUse 15 and Vitest 5 removals, Vapor options, public env secrets, SSR module state), or add a ready-made GitHub Actions CI that installs, lints, type-checks, tests, builds and checks these rules. Use before a release or upgrade, when a vue-skills-ci check fails, or when asked to set up CI for a Vue project.
KIMJINWOO4 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add KIMJINWOO4/vue-skills --skill vue-ci技能说明
name: vue-ci description: Run vue-skills-ci on a Vue or Nuxt project and fix what it reports (TypeScript 7 with vue-tsc, Pinia 4 and Vitest 5 peers, VueUse 15 and Vitest 5 removals, Vapor options, public env secrets, SSR module state), or add a ready-made GitHub Actions CI that installs, lints, type-checks, tests, builds and checks these rules. Use before a release or upgrade, when a vue-skills-ci check fails, or when asked to set up CI for a Vue project.
vue-ci
vue-skills-ci turns the version and safety rules from the vue-skills collection into checks that run locally and in GitHub Actions. It has no dependencies and needs Node 20 or newer.
Check a project
npx -y github:KIMJINWOO4/vue-skills-ci check # readable report
npx -y github:KIMJINWOO4/vue-skills-ci check --format json
Exit code 1 means at least one error. --fail-on warn makes warnings fail too, --fail-on never only reports.
Choose rules
The 19 rules are in six groups: toolchain, testing, vapor, vue, nuxt, security. Pick groups or rule ids with --rules and leave some out with --skip-rules; the workflow and action take the same values as rules and skip-rules inputs, and vue-skills-ci.config.json takes them as include and exclude.
npx -y github:KIMJINWOO4/vue-skills-ci rules # list groups and rules
npx -y github:KIMJINWOO4/vue-skills-ci check --rules toolchain,security
npx -y github:KIMJINWOO4/vue-skills-ci check --skip-rules pinia-store-destructure
When setting up CI for someone, ask which groups they want unless they said "all". toolchain and security suit every project; add testing, vue, nuxt and vapor when the project uses that part of the stack.
Fix findings
- Run the check with
--format jsonand group the findings byrule. - Fix errors first, then warnings. Info findings are advice.
- Each finding has
fix(what to do) anddocs(a vue-skills guide). If the vue-skills skills are installed, read the local copy: a docs URL ending inskills/<path>maps to the installed skill folder at the same path. - Re-run the check until it is clean, then run the project's own tests and build.
- A finding that is intended: add
// vue-skills-ci-disable-next-line <rule-id>above the line, or turn the rule off invue-skills-ci.config.json({ "rules": { "<rule-id>": "off" } }). Say why in a comment.
The rule list with explanations is in rules.
Add CI to a project
Write the workflow file, then commit it:
npx -y github:KIMJINWOO4/vue-skills-ci init --yes # full CI: install, lint, type-check, test, build, all rules
npx -y github:KIMJINWOO4/vue-skills-ci init --rules toolchain,security # full CI with chosen rule groups
npx -y github:KIMJINWOO4/vue-skills-ci init --rules-only --yes # only the rule check, for projects that already have CI
Agents should pass --yes or --rules; without them, init asks interactively when it runs in a terminal.
The full workflow calls the reusable workflow KIMJINWOO4/vue-skills-ci/.github/workflows/vue-ci.yml@v1. It detects pnpm, npm, Yarn or Bun from the lockfile and runs only the scripts that exist (lint, typecheck or type-check, test:unit or test, build-only or build). For a monorepo, set working-directory to the app folder.
Existing projects with many findings
Record the current findings so CI fails only on new ones:
npx -y github:KIMJINWOO4/vue-skills-ci check --baseline .vue-skills-ci-baseline.json --update-baseline
Commit the file and pass baseline: .vue-skills-ci-baseline.json to the workflow or action. Remove entries as you fix them by running the same command again.