Vue Admin Change Reviewer

Problem Solved

When changing a small filter, button, or form field in a Vue admin dashboard, the impact can easily reach query parameters, pagination reset, permission checks, dialog state, and API timing. These changes look small but may expose overwritten legacy logic, lost filter resets, or v-if rendering issues after release. vue-admin-change-reviewer reviews Vue 2 + Element UI / Vue 3 + Element Plus CRUD admin changes before implementation or after code is pasted, focusing on safe incremental updates instead of broad rewrites.

How It Works

It separates two review modes:
- Requirement-level review: with only a feature request, it provides risk predictions, likely affected areas, minimal-change suggestions, and a smoke-test checklist.
- Code-level review: with components, composables, stores, API calls, or templates, it identifies risky branches, state-sync issues, and side effects.

Its bias is conservative: add fields instead of rebuilding query models, reuse existing methods, preserve event chains and permission checks, and avoid large structural changes. It also checks filter reset, pagination reset, table refresh, button visibility, dialog/drawer state, hidden-form validation, tab side effects, and route parameter sync.

Boundaries

It fits small, urgent, or pre-release admin-panel changes on an existing codebase. Without code, it can only assess requirement-level risk. Large refactors, new architecture, or cross-platform changes need separate design work.