
rspack-tracing
Capture or analyze Rspack build traces to locate slow compiler phases, plugins, loaders, or the last events before a build failure.
- Installs
- 279
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/rstackjs/agent-skills --skill rspack-tracing- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads rspack-tracing automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Rspack tracing & performance profiling
When to use this skill
Use this skill when you need to:
- Diagnose why an Rspack build is slow.
- Understand which plugins or loaders are taking the most time.
- Analyze a user-provided Rspack trace file.
- Guide a user to capture a performance profile.
Workflow
1. Capture a trace
First, ask the user to run their build with tracing enabled.
# Set environment variables for logging to a file
RSPACK_PROFILE=TRACE RSPACK_TRACE_LAYER=logger RSPACK_TRACE_OUTPUT=./trace.json pnpm build
This will generate a trace file in a timestamped directory like .rspack-profile-{timestamp}-{pid}/trace.json.
See references/tracing-guide.md for more details on configuration.
2. Quick diagnosis for Crashes/Errors
If the user wants to identify which stage a crash or error occurred in, use tail to quickly view the last events without running the full analysis:
# Navigate to the generated profile directory
cd .rspack-profile-*/
# View the last 20 events to see where the build failed
tail -n 20 trace.json
The last events will show the span names and targets where the build stopped, helping to quickly pinpoint the problematic stage, plugin, or loader.
3. Full performance analysis
For detailed performance profiling (not just crash diagnosis), ask the user whether to run the bundled scripts/analyze_trace.mjs on the generated trace file. If they agree, resolve it relative to the Skill root while keeping the working directory in the user's project, then run:
# Navigate to the generated profile directory
cd .rspack-profile-*/
# Run the analysis script
node "<skill-root>/scripts/analyze_trace.mjs" trace.json
4. Interpret results
Use the output from the script to identify bottlenecks. Consult references/bottlenecks.md to map span names to actionable fixes.
5. Locate slow plugins
Based on the "Top Slowest Hooks" from the analysis script:
- Identify the Hook: Note the hook name (e.g.,
hook:CompilationOptimizeChunks). - Inspect Configuration: Read
rspack.config.jsorrsbuild.config.ts. - Map Hook to Plugin: Look for plugins and their sources that tap into that specific hook.
- Output: Output the paths, lines and columns of the suspected plugin source code.
Common scenarios & quick fixes
- Bottleneck Reference: Mapping spans to concepts.
- Tracing Guide: Detailed usage of
RSPACK_PROFILE.
FAQ
What does the rspack-tracing skill do?
Capture or analyze Rspack build traces to locate slow compiler phases, plugins, loaders, or the last events before a build failure.
How do I install rspack-tracing?
Run npx skills add https://github.com/rstackjs/agent-skills --skill rspack-tracing in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/rspack-tracing/ (personal) or .claude/skills/rspack-tracing/ (project).
Which AI agents can use rspack-tracing?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is rspack-tracing safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains rspack-tracing?
It is published by rstackjs in rstackjs/agent-skills. It has 279 recorded installs.
More from rstackjs/agent-skills
rsbuild-best-practices
rstackjs/agent-skills
Configure, review, or troubleshoot Rsbuild applications, including build/dev commands, assets, type checking, and bundle optimization.
rstest-best-practices
rstackjs/agent-skills
Set up, write, or review Rstest tests and configuration, including environments, mocks, snapshots, coverage, and CI.
rslib-best-practices
rstackjs/agent-skills
Configure, review, or troubleshoot Rslib library builds, output formats, declarations, dependency handling, and integrations.
rspack-best-practices
rstackjs/agent-skills
Configure, review, or troubleshoot Rspack builds, including loaders, CSS, assets, type checking, bundle optimization, and profiling.
rspress-best-practices
rstackjs/agent-skills
Configure, review, or troubleshoot Rspress v2 sites, including content conventions, navigation, MDX, assets, search, and deployment.
rspack-v2-upgrade
rstackjs/agent-skills
Use when upgrading a Rspack 1.x project to v2, including dependency and configuration updates.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available