Bundle Analyzer Agent Skill: Add analyzer skill (#99169)
## Summary Add a model-discoverable browser initial-load optimizer for slow route startup, oversized client bundles, duplicate browser dependencies and interaction-gated features. The skill follows six ordered steps with observable completion gates: scope, baseline, validation, candidate, one verified fix, report. Audit is the default and leaves app source/dependencies/lockfiles unchanged; fixing requires an explicit request. The shared workflow keeps capture/replay (including saved-snapshot reuse), a complete `--route` command, installed-schema validation and evidence-qualified reporting visible. The v1 schema in the app's installed `next` package remains the field/record authority; the skill covers complete-stream, join and source checks that per-record validation cannot establish. Optional CLI choices defer to installed `next analyze --help`. Conditional plain references carry graph clustering/min-cut procedures and lazy-feature/package-dedupe/server-display checks. Agents load them only when the candidate reaches that branch. The main skill is 49% shorter by character count, preserving authorization, graph completeness and behavior safeguards. Related-skill pointers sit beside their triggering branches. This PR owns the skill and AI-agent guide entry; the root/producer PRs own CLI/schema/data contracts. ## Verification - Prettier, skill/reference language lint, frontmatter/invocation checks, six completion gates, relative-pointer checks and installed-like recursive file discovery pass. Static scenario walkthroughs cover audit/fix, saved replay, custom directories, blocked/corrupt exports, incomplete graph evidence and each fix branch. The existing eval installer copies skill reference files recursively. - This writing-only pass changes four Markdown files across the eight skill-bearing layers; the root, installed schema, runtime/Rust, evals, tests and executable modes are unchanged. No removed unit suite is reintroduced. Earlier no-emit/runtime-probe/package checks are separate evidence, not rerun for prose. - Full model-driven evals and native e2e were not run locally. Shorter text and static checks are not evidence of better agent outcomes. New-head CI must establish its own status. <!-- NEXT_JS_LLM --> <!-- fleet d7bdbc2b-b0bc-4591-99eb-dccb0fa49c73 --> --------- Co-authored-by:vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by:
Will Binns-Smith <755844+wbinnssmith@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment