vue-review
Skill28 starsChanged 32 days agoMITView on GitHub
Review Vue and Nuxt code changes. A prioritized checklist for pull requests and diffs touching .vue files, composables, Pinia stores, routes and Nuxt server code, covering correctness, reactivity, SSR safety, security, accessibility, performance and maintainability, with findings reported as file:line plus a fix. Use when asked to review, audit or check Vue code, a PR or a diff.
In this repository16 other files it gives its agents.
- antfuSkill
- build-toolingSkill
- designSkill
- find-skillsSkill
- nuxtSkill
- vitepressSkill
- vue-a11ySkill
- vue-ciSkill
- vue-clean-componentsSkill
- vue-dataSkill
- vue-debugSkill
- vue-formsSkill
- vue-performanceSkill
- vueSkill
- vue-uiSkill
- vue-upgradeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Learn the project's conventions: before judging style: Vue and Nuxt majors, Options or Composition API, lint config, UI library, data layer.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Vue Code Review
Process
- Scope. Get the diff (
git diff <base>...HEAD, or the PR). List the changed.vue,.ts, store, route andserver/files. Read each changed component in full, not only the hunk, because template and script interact. - Learn the project's conventions before judging style: Vue and Nuxt majors, Options or Composition API, lint config, UI library, data layer. Do not flag a convention the codebase uses on purpose.
- Walk the checklist in priority order (checklist). Stop to verify each suspected problem by reading the code path; drop anything you cannot point to.
- Report using the format below. Lead with blockers. Skip praise and restating what the diff does.
Priorities
| Priority | Area | Typical findings |
| P0 blocker | Correctness and security | Lost reactivity, mutated props, v-html on user input, secrets in client bundles, SSR state shared between requests, missing await on navigation or data |
| P1 major | Runtime behavior | Hydration mismatches, effects without cleanup, watchers that should be computed, race conditions in fetches, broken keyboard access |
| P2 minor | Maintainability and performance | Oversized components, prop drilling, duplicated state, unkeyed or index-keyed lists that reorder, deep watchers on large data |
| P3 nit | Style | Naming, ordering of SFC blocks, comments. Report only if the project's lint does not already cover it |
Report format
[P0] src/components/UserCard.vue:42
Destructuring `props` in setup loses reactivity; the card keeps showing the first user after navigation.
Fix: use `props.user` in the template, or `const { user } = toRefs(props)`.One finding per block: priority, file:line, what goes wrong for the user, and the concrete fix. End with a one-line summary: counts per priority and whether the change is safe to merge.
Out of scope
Pure formatting already handled by ESLint or Prettier, and rewrites to personal taste. For a deeper accessibility audit use vue-a11y; for measured performance work use vue-performance.
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
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.

