Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Data & analytics

rsdoctor-analysis

Use when analyzing Rspack/Webpack bundles from local `rsdoctor-data.json` and producing evidence-based optimization recommendations.

rstackjs · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add rstackjs/agent-skills --skill rsdoctor-analysis

About this skill


name: rsdoctor-analysis description: Use when analyzing Rspack/Webpack bundles from local rsdoctor-data.json and producing evidence-based optimization recommendations.

Rsdoctor Analysis Assistant Skill

Use the globally installed rsdoctor-agent CLI from @rsdoctor/agent-cli only after a real rsdoctor-data.json path exists. Keep analysis read-only unless the user explicitly asks for install/config setup.

Response order (required): High-Priority Issues -> Proposed Solutions -> Optional Reference-Chain Follow-up Choices -> Next Deep-Dive Issue Categories (Not commands).

Core Workflow

  1. Reuse current-session results and valid .rsdoctor-analysis-cache.json entries before doing new work.
  2. Locate rsdoctor-data.json fast: user-provided path, then dist/rsdoctor-data.json, output/rsdoctor-data.json, static/rsdoctor-data.json, .rsdoctor/rsdoctor-data.json, then one bounded rg --files search excluding node_modules and .git. Treat manifest.json only as an index.
  3. If data exists, skip all plugin version/config/build generation logic. Update cache when useful.
  4. If data is missing, stop analysis: do not run rsdoctor-agent analysis commands, do not run the Analysis Gate, and either ask for the data path or run the Generation Gate below only when setup/generation is required.
  5. After a real data file exists, run Analysis Gate at most once before the first rsdoctor-agent data-fetch command: verify global @rsdoctor/agent-cli with npm view @rsdoctor/agent-cli version and rsdoctor-agent --version; install latest only if missing/outdated, a version-related error occurs, or the user asks to refresh.
  6. Fetch only the Default Evidence Set first; run independent fetches in parallel when possible.
  7. Run the ROI Triage Gate below before selecting deep-dive commands or recommendations. Use it to rank issue categories by measured impact, then synthesize findings in the required response order.

Performance rules: parallelize independent checks, cache only derived facts (dataFile, dataFileMtime, pluginName, pluginVersion, dependency/config/plugin modification times), and invalidate cache when paths disappear, modification times change, the user asks to refresh, or cached values fail. Speculative plugin checks must not trigger generation; use them only after confirming the data file is missing.

ROI Triage Gate

Before recommending fixes, classify the current build into broad cost buckets and choose the highest-ROI lever from evidence, not intuition. This gate is generic for Rspack/Webpack projects; do not use framework-specific runtime layers unless the user's project exposes them in the data.

Cost bucketEvidence sourceFirst lever
Assets/mediaassetsTop, assets media, chunkGraph.assetsCompress, convert, deduplicate, subset, or lazy-load large assets
Large packages/modulespackagesTop, module/package size fieldsReplace heavy packages, use deep imports, split non-critical code, or review direct dependency choices
Duplicate/cross-chunk costE1001/E1002, packages duplicates, cross-chunk package summariesDeduplicate versions, tune package resolution, or adjust splitChunks/cache groups
Tree-shaking wasteretainedModulesTop, retained CJS/barrel/side-effects modulesFix CJS/barrel imports, sideEffects declarations, or package entrypoints
Build-time costbuildCost, loaders/plugins/directories cost dataOptimize loaders/plugins, cache, watcher, or source-map/dev settings; prioritize only when the user asks about build performance

Decision rules:

  • Report the measured breakdown first when it changes recommendation priority.
  • Start with the largest bucket that maps to a practical fix; a smaller issue should not outrank a larger one unless the larger one is expected or intentionally unavoidable.
  • Treat issuer/reference-chain tracing as second-pass work. Run it only when a high-impact candidate needs ownership evidence, or when the user asks "why" / "who imported this".
  • Do not present aggregate rule output as sufficient evidence for a fix that requires a concrete file, package, chunk, size, or dependency path.
  • If the largest bucket is structural or intentionally required, say that it is a wall and name the external change that would be needed instead of inventing low-impact source edits.

Generation Gate

Identify pluginName (@rsdoctor/rspack-plugin or @rsdoctor/webpack-plugin) and determine pluginVersion from local files first: package.json, lockfile, then node_modules/<plugin>/package.json; use pnpm why / npm ls only as fallback.

Use this exact if/else decision tree; do not merge branches:

if pluginName is missing:
  install/register the matching Rsdoctor plugin, then configure output.mode='brief' and output.options.type=['json']; build with RSDOCTOR=true only
else if pluginVersion is unknown:
  resolve pluginVersion first; if still unknown, configure output.mode='brief' and output.options.type=['json']; build with RSDOCTOR=true only
else if pluginVersion >= 1.5.11:
  do not edit plugin config just for JSON; build with RSDOCTOR_OUTPUT=json and RSDOCTOR=true if needed
else: # pluginVersion < 1.5.11
  MUST configure output.mode='brief' and output.options.type=['json']; 
Read the complete source ↗