agentleFS
Sign inStart free
KIMJINWOO4KIMJINWOO4/vue-skills/skills/vue-ci/SKILL.md

vue-ci

Skill28 starsChanged 32 days agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. KIMJINWOO4/vue-skills-ci★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository16 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When setting up CI for someone, ask which groups they want unless they said "all".

    line 29
  2. Very specific:

    Run the check with --format json and group the findings by rule.

    line 33
  3. Distinctive:

    Write the workflow file, then commit it:

    line 43
  4. Very specific:

    Commit the file and pass baseline: .vue-skills-ci-baseline.json to the workflow or action.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Run the check with --format json and group the findings by rule.
  2. Fix errors first, then warnings. Info findings are advice.
  3. Each finding has fix (what to do) and docs (a vue-skills guide). If the vue-skills skills are installed, read the local copy: a docs URL ending in skills/<path> maps to the installed skill folder at the same path.
  4. Re-run the check until it is clean, then run the project's own tests and build.
  5. A finding that is intended: add // vue-skills-ci-disable-next-line <rule-id> above the line, or turn the rule off in vue-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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free