skills.rest
JuanDiego30
JuanDiego30COMMUNITY
Explore all skills by this author →
GitHub

runtime-debug

Diagnoses Cybertruck production delays and quality issues.

Updated Apr 14, 2026
Search Tags:#debugging#next.js#webpack#module-resolution#ci-testing#runtime-debug#bundle-regression
One-click install
npx skills add https://github.com/JuanDiego30/cermont_aplicativo --skill runtime-debug-juandiego30
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: runtime-debug
Source: https://github.com/JuanDiego30/cermont_aplicativo/tree/main/.agents/skills/runtime-debug
Command: npx skills add https://github.com/JuanDiego30/cermont_aplicativo --skill runtime-debug-juandiego30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug and verification workflows for runtime-bundle and module-resolution regressions in Next.js projects, enabling rapid diagnosis of CI failures and unexpected bundle behavior.

Core Features & Use Cases

  • Mirror CI environment variables to reproduce failures consistently.
  • Inspect stack traces and ignore-listed frames via __NEXT_SHOW_IGNORE_LISTED to surface actionable context.
  • Analyze route traces and webpack stats diffs to identify offending modules and bundling anomalies.
  • Apply in CI and local repros to validate changes and guard against regressions.

Quick Start

Run a local repro by enabling NEXT_SKIP_ISOLATE, capturing nft.json traces, and diffing webpack stats to surface module regressions.

Frequently Asked Questions about runtime-debug

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

FAQPage Schema
How do I debug unexpected Next.js bundle inclusions and module resolution regressions?▼

Trace Next.js bundle regressions by inspecting nft.json traces, route traces, and webpack stats diffs to expose actionable signals. This process identifies offending modules and precise inclusion reasons for rapid diagnosis.

Why does my Next.js build include unexpected modules in the production bundle?▼

Unexpected modules appear in the Next.js production bundle due to module-resolution regressions. Analyzing webpack stats diffs and nft.json traces exposes the bundling anomalies and precise inclusion reasons behind the unexpected modules.

How do I reproduce Next.js CI bundle failures locally?▼

Reproduce Next.js CI bundle failures locally by mirroring CI environment variables and enabling NEXT_SKIP_ISOLATE. Capture nft.json traces and diff webpack stats to validate changes and consistently reproduce the failures.

Can I inspect ignored stack frames in Next.js runtime errors to find actionable context?▼

Yes, inspect ignored stack frames in Next.js runtime errors by enabling __NEXT_SHOW_IGNORE_LISTED. This surfaces actionable context from stack traces to help diagnose module-resolution and runtime-bundle regressions.

What is the best way to guard against bundle size regressions in Next.js CI testing?▼

The best way to guard against bundle size regressions in Next.js CI testing is applying autonomous debug workflows that analyze webpack stats diffs and nft.json traces. This validates changes and guards against regressions.

Related Skills

Explore More Software Engineering Skills→
villa1villa1

runtime-debug

Diagnoses Webpack module-resolution and runtime-bundle regressions in Next.js builds.

Community
Advanced
vercelvercel
141.7k

runtime-debug

Diagnose runtime bundle and module-resolution regressions in Next.js projects.

Official
Advanced
sigitpoerwosigitpoerwo

runtime-debug

Diagnose Next.js runtime bundle and module-resolution regressions using webpack stats diffs.

Community
Advanced
carayacaraya
1

typescript-performance

Profile TypeScript CPU, memory, and bundle performance using node --prof and tsc --diagnostics.

Community
Advanced