Agent skill

Runtime Debug

by OpenHikmah in OpenHikmah/openhikmah-web

Debug and verification workflow for runtime-bundle and module-resolution regressions.

GPL-3.0Auto-check passedDevelopment

Install Runtime Debug

skills CLI
$ npx skills add OpenHikmah/openhikmah-web --skill runtime-debug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install OpenHikmah/openhikmah-web runtime-debug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/OpenHikmah/openhikmah-web.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/runtime-debug .claude/skills/runtime-debug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
runtime-debug
GitHub stars
181
Token cost
~618 tokens
SKILL.md length
205 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
GPL-3.0

At a glance

Debug and verification workflow for runtime-bundle and module-resolution regressions.

  • Works in 3 steps: Inspect route trace artifacts… → Inspect traced server chunks for… → Add a test-start-webpack assertion that…
  • Diagnosing unexpected module inclusions
  • SKILL.md covers Local Repro Discipline, Stack Trace Visibility, User-Bundle Regression Guardrail and Bundle Tracing / Inclusion Proof, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Runtime Debug is an agent skill from OpenHikmah/openhikmah-web. Debug and verification workflow for runtime-bundle and module-resolution regressions. Use when diagnosing unexpected module inclusions, bundle size regressions, or CI failures related to NEXTSKIPISOLATE, nft.json traces, or runtime bundle selection (module.compiled.js). Covers CI env mirroring, full stack traces via NEXTSHOWIGNORELISTED, route trace inspection, and webpack stats diffing.

Its SKILL.md is about 620 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging, Failing and flaky tests and Crypto and DeFi analysis. It works with webpack, Next.js and TypeScript. The repository describes itself as: An AI-powered Quran knowledge graph — place verses on a canvas and discover thematic, linguistic, and theological connections. The licence is GPL-3.0.

When your agent uses it

  • Diagnosing unexpected module inclusions
  • Bundle size regressions
  • CI failures related to NEXTSKIPISOLATE
  • Nft.json traces

Example prompts

  • “/runtime-debug”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Inspect route trace artifacts (.next/server/.../page.js.nft.json).
  2. Inspect traced server chunks for forbidden internals (e.g. next/dist/server/stream-utils/node-stream-helpers.js, node:stream/promises).
  3. Add a test-start-webpack assertion that reads the route trace and traced server chunks, and fails on forbidden internals. This validates…

What it can do on your machine

Read from SKILL.md and the folder at commit 0e3a65e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Runtime Debug loads about 618 tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 205 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~618

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OpenHikmah/openhikmah-web at commit 0e3a65e, republished under its GPL-3.0 licence (© OpenHikmah). 205 words, ~618 tokens.

Download SKILL.mdSave it as .claude/skills/runtime-debug/SKILL.md (or your agent's skills folder).
name
runtime-debug
description
Debug and verification workflow for runtime-bundle and module-resolution regressions. Use when diagnosing unexpected module inclusions, bundle size regressions, or CI failures related to NEXT_SKIP_ISOLATE, nft.json traces, or runtime bundle selection (module.compiled.js). Covers CI env mirroring, full stack traces via __NEXT_SHOW_IGNORE_LISTED, route trace inspection, and webpack stats diffing.
metadata.internal
true

Runtime Debug

Use this skill when reproducing runtime-bundle, module-resolution, or user-bundle inclusion regressions.

Local Repro Discipline

  • Mirror CI env vars when reproducing CI failures.
  • Key variables: IS_WEBPACK_TEST=1 forces webpack (turbopack is default), NEXT_SKIP_ISOLATE=1 skips packing next.js.
  • For module-resolution validation, always rerun without NEXT_SKIP_ISOLATE=1.

Stack Trace Visibility

Set __NEXT_SHOW_IGNORE_LISTED=true to disable the ignore-list filtering in dev server error output. By default, Next.js collapses internal frames to at ignore-listed frames, which hides useful context when debugging framework internals. Defined in packages/next/src/server/patch-error-inspect.ts.

User-Bundle Regression Guardrail

When user next build starts bundling internal Node-only helpers unexpectedly:

  1. Inspect route trace artifacts (.next/server/.../page.js.nft.json).
  2. Inspect traced server chunks for forbidden internals (e.g. next/dist/server/stream-utils/node-stream-helpers.js, node:stream/promises).
  3. Add a test-start-webpack assertion that reads the route trace and traced server chunks, and fails on forbidden internals. This validates user-project bundling (not publish-time runtime bundling).

Bundle Tracing / Inclusion Proof

To prove what user bundling includes, emit webpack stats from the app's next.config.js:

js
// next.config.js
module.exports = {
  webpack(config) {
    config.profile = true
    return config
  },
}

Then use stats.toJson({ modules: true, chunks: true, reasons: true }) and diff webpack-stats-server.json between modes. This gives concrete inclusion reasons (e.g. which module required node:stream/promises) and is more reliable than analyzer HTML alone.

  • $flags - flag wiring (config/schema/define-env/runtime env)
  • $dce-edge - DCE-safe require patterns and edge constraints
  • $react-vendoring - entry-base boundaries and vendored React

© OpenHikmah, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/runtime-debug of OpenHikmah/openhikmah-web.

Open the folder on GitHubat commit 0e3a65e

Compare with similar skills

Runtime Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Runtime Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Runtime Debug this skillOpenHikmah/openhikmah-web181—~618Automated safety check: PassGPL-3.0
Failure Oriented InstrumentationArabelaTso/Skills-4-SE253—~2.1kAutomated safety check: PassApache-2.0
Dbgtheodo-group/debug-that158—~1.9kAutomated safety check: PassMIT
Suede Code ReviewJasonColapietro/suede-creator-skills127—~7.1kAutomated safety check: PassMIT
Playwright Coretestdino-hq/playwright-skill3851 repos~1.4kAutomated safety check: PassMIT
Playwrightpproenca/dot-skills214—~1.7kAutomated safety check: PassMIT

Similar skills

  • Failure Oriented Instrumentation

    ArabelaTso/Skills-4-SE

    Selectively instruments code to capture runtime data for debugging failures and bugs.

    253 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Dbg

    theodo-group/debug-that

    Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.

    158 GitHub stars~1.9k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Suede Code Review

    JasonColapietro/suede-creator-skills

    Suede AI findings-only code review with full context: changed files, callers, contracts, and deploy surface.

    127 GitHub stars~7.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Playwright Core

    testdino-hq/playwright-skill

    Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests.

    385 GitHub starsUsed in 1 repo~1.4k tokens
    Testing & QAAuto-check passed
  • Playwright

    pproenca/dot-skills

    Playwright testing best practices for Next.js applications (formerly test-playwright).

    214 GitHub stars~1.7k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • React Router Bug Fix Workflow

    remix-run/react-router

    Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.

    57k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

Questions about Runtime Debug

What does Runtime Debug do?

Debug and verification workflow for runtime-bundle and module-resolution regressions. Runtime Debug is an agent skill from OpenHikmah/openhikmah-web. Debug and verification workflow for runtime-bundle and module-resolution regressions.

When should I use Runtime Debug?

Runtime Debug fits situations like: diagnosing unexpected module inclusions; bundle size regressions; CI failures related to NEXTSKIPISOLATE; nft.json traces.

How do I install Runtime Debug in Claude Code?

Run `npx skills add OpenHikmah/openhikmah-web --skill runtime-debug -a claude-code`. Or copy the skill folder (.agents/skills/runtime-debug in OpenHikmah/openhikmah-web) into .claude/skills/runtime-debug in your project. Claude Code loads it when a task matches its description.

How do I install Runtime Debug in Codex?

Run `npx skills add OpenHikmah/openhikmah-web --skill runtime-debug -a codex`. Or copy the skill folder (.agents/skills/runtime-debug in OpenHikmah/openhikmah-web) into .agents/skills/runtime-debug in your project. Codex loads it when a task matches its description.

Can I use Runtime Debug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenHikmah/openhikmah-web --skill runtime-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/runtime-debug, .gemini/skills/runtime-debug, .github/skills/runtime-debug and .opencode/skills/runtime-debug in your project.

What does Runtime Debug need to run?

SKILL.md names no scripts, command-line tools or credentials: Runtime Debug is instructions for the agent only.

Does Runtime Debug access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Runtime Debug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Runtime Debug use?

Runtime Debug is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Runtime Debug use?

About 618 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Runtime Debug?

Skills that share tags, products or a category with Runtime Debug: Failure Oriented Instrumentation (ArabelaTso/Skills-4-SE, 253 stars), Dbg (theodo-group/debug-that, 158 stars), Suede Code Review (JasonColapietro/suede-creator-skills, 127 stars) and Playwright Core (testdino-hq/playwright-skill, 385 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Runtime Debug?

OpenHikmah (a GitHub organization) maintains it in OpenHikmah/openhikmah-web, which has 181 GitHub stars. The repository was last updated on October 7, 2026.

Source: OpenHikmah/openhikmah-web on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.