vite-build-qa-engineer

Verify Vite production bundles for secret leakage and preview parity.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill vite-build-qa-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite-build-qa-engineer
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/vite-build-qa-engineer
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill vite-build-qa-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill verifies the production Vite artifact itself so you can catch secret leaks, broken preview behavior, and build-only regressions before deployment.

Core Features & Use Cases

  • Secret exposure auditing: Checks VITE_-prefixed environment variables, define replacements, plugin injections, and built dist output for leaked values and secret-shaped patterns.
  • Build and preview validation: Confirms the real build mode, preview parity, SPA fallback routing, base-path asset loading, dynamic imports, and mode-dependent behavior.
  • Output inspection: Reviews bundle size, unexpected inclusions, and production sourcemap policy to ensure the shipped artifact matches release expectations.
  • Use case: Use this Skill when an app works in dev but fails after build, when you need to prove no secrets landed in the client bundle, or when CI must gate release artifacts with evidence.

Quick Start

Ask the skill to run the real Vite production build for the deploy mode, inspect the dist output for secret exposure, and verify preview routing and asset parity before release.

Frequently Asked Questions about vite-build-qa-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Vite build for secret leaks before deployment?

To check a Vite build for secret leaks, audit VITE_-prefixed environment variables, define replacements, and the built dist output for leaked values. This validates that no secrets landed in the client bundle before deployment.

Why does my Vite app work in dev but fail after build with routing errors?

Vite apps fail after build due to preview parity issues or broken SPA fallback routing. Verifying the real production build mode and testing base-path asset loading confirms preview routing matches release expectations.

What is the best way to validate Vite production sourcemap policy and bundle size?

The best way to validate Vite sourcemap policy and bundle size is inspecting the production output artifact. Reviewing the built dist output confirms sourcemap settings and flags unexpected inclusions matching release expectations.

Can I gate my CI pipeline with evidence-based Vite build checks?

Yes, you can gate CI pipelines with evidence-based Vite build checks. Running a real production build for the deploy mode and inspecting dist output provides evidence that no secrets leaked and preview routing works before release.

Does Vite build QA catch secret-shaped patterns injected by plugins?

Yes, Vite build QA catches secret-shaped patterns injected by plugins. The verification searches the built dist output and plugin injections for secret exposure, ensuring no leaked values from environment variables or define replacements ship to production.

When do I need to verify Vite preview parity and dynamic imports?

You need to verify Vite preview parity and dynamic imports when an app works in dev but fails after build. Validating mode-dependent behavior, SPA fallback routing, and dynamic imports in the real build mode confirms production output integrity before deployment.