Agent skill

Extempore JIT Debugging Guide

by digego in digego/extempore

Debugging guide for Extempore covering its three layers, compilation paths, startup sequence and the batch, eval and interactive modes used to isolate JIT problems.

No licenceAuto-check passedDevelopment

Install Extempore JIT Debugging Guide

skills CLI
$ npx skills add digego/extempore --skill extempore-debugging -a claude-code

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

GitHub CLI
$ gh skill install digego/extempore extempore-debugging --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/digego/extempore.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/extempore-debugging .claude/skills/extempore-debugging && 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
extempore-debugging
GitHub stars
1.5k
Token cost
~4.4k tokens
SKILL.md length
1,659 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
None found

At a glance

Debugging guide for Extempore covering its three layers, compilation paths, startup sequence and the batch, eval and interactive modes used to isolate JIT problems.

  • Works in 3 steps: C++ runtime (src/): Scheme interpreter,… → Scheme runtime (runtime/): scheme.xtm,… → xtlang libraries (libs/): user-facing…
  • Debugging JIT compilation failures in Extempore
  • SKILL.md covers Architecture overview, Compilation paths, Startup sequence and Key flags, plus 11 more sections
  • Calls cmake, ffprobe and ffmpeg

What it does

Extempore has a C++ runtime holding the Scheme interpreter, LLVM JIT and audio and OSC support, a Scheme runtime, and xtlang libraries on top. The skill explains the interactive compilation path from llvm:compile-ir into the JIT, the AOT path that queues IR when an output port is set, and the startup sequence from main through the init files to loading the base library and the AOT cache.

Key flags help isolate bugs: skipping the base library, disabling audio for headless CI, running a single-process batch expression, evaluating at startup while keeping the TCP server, and rendering DSP output to a WAV file with an optional duration cap. Batch and eval modes differ in process setup, so type-inference bugs may reproduce in one and not the other, and the guide advises testing in both.

When your agent uses it

  • Debugging JIT compilation failures in Extempore
  • Tracking symbols through the interactive and AOT compilation paths
  • Reproducing a bug in batch mode versus eval mode
  • Running Extempore headless in CI, optionally rendering audio to a WAV file

Example prompts

  • “My xtlang function fails to compile under eval but works in batch mode, so help me work out why.”
  • “Run Extempore with the nobase and noaudio flags to test JIT compilation in isolation.”
  • “Render the DSP output to a WAV file in a headless run and stop it after ten seconds.”

Requirements

  • A built Extempore with its source tree

Workflow steps

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

  1. C++ runtime (src/): Scheme interpreter, LLVM JIT, audio/OSC
  2. Scheme runtime (runtime/): scheme.xtm, llvmir.xtm, llvmti.xtm
  3. xtlang libraries (libs/): user-facing compiled DSL code

What it can do on your machine

Read from SKILL.md and the folder at commit 5e42e31. 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

    Shell commands in SKILL.md call:

    • cmake
    • ffprobe
    • ffmpeg

    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

Extempore JIT Debugging Guide loads about 4.4k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 1,659 words of instructions outside code blocks.

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

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,659 words (~4,445 tokens).

name
extempore-debugging

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/extempore-debugging of digego/extempore.

Open the folder on GitHubat commit 5e42e31

Compare with similar skills

Extempore JIT Debugging Guide 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.

Extempore JIT Debugging Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Extempore JIT Debugging Guide this skilldigego/extempore1.5k—~4.4kAutomated safety check: PassNone
OpenROAD Bug FixerThe-OpenROAD-Project/OpenROAD3.2k—~784Automated safety check: PassBSD-3-Clause
Debugging CodeJetBrains/skills3631 repos~3.8kAutomated safety check: PassNone
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT

Similar skills

  • OpenROAD Bug Fixer

    The-OpenROAD-Project/OpenROAD

    Fixes an OpenROAD bug from a GitHub issue or error code: finds the root cause, implements the fix, adds a regression test and prepares a signed-off commit.

    3.2k GitHub stars~784 tokensUpdated today
    DevelopmentAuto-check passed
  • Debugging Code

    JetBrains/skills

    Official

    A skill your agent uses for debugger-driven runtime root-cause analysis in Rider-supported solutions and projects, including .NET/C, F, VB, C++, Unity, Unreal Engine, and other GameDev or…

    363 GitHub starsUsed in 1 repo~3.8k tokens
    Game DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 3 days ago
    DevelopmentAuto-check: notes
  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed

Works with

Categories

Questions about Extempore JIT Debugging Guide

What does Extempore JIT Debugging Guide do?

Debugging guide for Extempore covering its three layers, compilation paths, startup sequence and the batch, eval and interactive modes used to isolate JIT problems. Extempore has a C++ runtime holding the Scheme interpreter, LLVM JIT and audio and OSC support, a Scheme runtime, and xtlang libraries on top. The skill explains the interactive compilation path from llvm:compile-ir into the JIT, the AOT path that queues IR when an output port is set, and the startup sequence from main through the init files to loading the base library and the AOT cache.

When should I use Extempore JIT Debugging Guide?

Extempore JIT Debugging Guide fits situations like: debugging JIT compilation failures in Extempore; tracking symbols through the interactive and AOT compilation paths; reproducing a bug in batch mode versus eval mode; running Extempore headless in CI, optionally rendering audio to a WAV file.

How do I install Extempore JIT Debugging Guide in Claude Code?

Run `npx skills add digego/extempore --skill extempore-debugging -a claude-code`. Or copy the skill folder (.claude/skills/extempore-debugging in digego/extempore) into .claude/skills/extempore-debugging in your project. Claude Code loads it when a task matches its description.

How do I install Extempore JIT Debugging Guide in Codex?

Run `npx skills add digego/extempore --skill extempore-debugging -a codex`. Or copy the skill folder (.claude/skills/extempore-debugging in digego/extempore) into .agents/skills/extempore-debugging in your project. Codex loads it when a task matches its description.

Can I use Extempore JIT Debugging Guide 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 digego/extempore --skill extempore-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/extempore-debugging, .gemini/skills/extempore-debugging, .github/skills/extempore-debugging and .opencode/skills/extempore-debugging in your project.

What does Extempore JIT Debugging Guide need to run?

Going by SKILL.md and its folder, Extempore JIT Debugging Guide needs the command-line tools its instructions call (cmake, ffprobe and ffmpeg). Our summary lists: A built Extempore with its source tree.

Does Extempore JIT Debugging Guide 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 Extempore JIT Debugging Guide 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 Extempore JIT Debugging Guide use?

No licence was found for Extempore JIT Debugging Guide or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Extempore JIT Debugging Guide use?

About 4.4k tokens (SKILL.md is roughly 18k 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 Extempore JIT Debugging Guide?

Skills that share tags, products or a category with Extempore JIT Debugging Guide: OpenROAD Bug Fixer (The-OpenROAD-Project/OpenROAD, 3.2k stars), Debugging Code (JetBrains/skills, 363 stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars) and Bug Finder for daisyUI (saadeghi/daisyui, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Extempore JIT Debugging Guide?

digego (a GitHub user) maintains it in digego/extempore, which has 1,464 GitHub stars. The repository was last updated on September 24, 2026.

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