skills.rest
saskenuba
saskenubaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

flowstorm-debugger

Record and inspect Clojure runtime data with FlowStorm APIs.

1|Updated Aug 16, 2018
Search Tags:#timeline#instrumentation#debugger#recording#clojure#flowstorm#runtime-analysis
One-click install
npx skills add https://github.com/saskenuba/dotfiles --skill flowstorm-debugger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flowstorm-debugger
Source: https://github.com/saskenuba/dotfiles/tree/main/ai/.claude/skills/flowstorm-debugger
Command: npx skills add https://github.com/saskenuba/dotfiles --skill flowstorm-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FlowStorm Debugger enables developers to analyze Clojure program executions by recording and inspecting runtime data, turning runtime traces into actionable insights.

Core Features & Use Cases

  • Timeline exploration of function calls, returns, and unwinds to understand program flow.
  • Value inspection of arguments, results, and exceptions for targeted debugging.
  • Use Case: While debugging a performance issue, connect FlowStorm, start recording, instrument the namespace, reload code, and replay the flow to locate bottlenecks.

Quick Start

Connect FlowStorm, start recording, instrument namespaces in the FlowStorm UI, reload the namespace, run your function, and review the timeline in the UI or via runtime APIs.

Frequently Asked Questions about flowstorm-debugger

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

FAQPage Schema
How do I debug Clojure applications by recording runtime execution data?▼

To debug Clojure applications by recording runtime execution data, connect FlowStorm, start recording, instrument the target namespaces, reload the code, and then run your function to capture its execution flow.

Can I inspect function arguments and return values in a ClojureScript timeline?▼

Yes, you can inspect function arguments, return values, and exceptions in a ClojureScript timeline by exploring the recorded flow data to trace function calls, returns, and unwinds for targeted debugging.

What is the process for tracing Clojure program flows to locate performance bottlenecks?▼

Tracing Clojure program flows to locate performance bottlenecks involves connecting FlowStorm, instrumenting namespaces, reloading code, running the function, and replaying the timeline to inspect runtime values and identify slow execution paths.

Does FlowStorm runtime analysis require specific namespace instrumentation before recording?▼

Yes, FlowStorm runtime analysis requires you to instrument namespaces in the FlowStorm UI and reload the code before running your functions to ensure the execution timeline captures the targeted runtime data.

Can I query recorded flow data via APIs instead of using the FlowStorm UI?▼

Yes, you can query recorded flow data via runtime APIs, enabling you to programmatically inspect function traces, arguments, and results without relying solely on the visual FlowStorm timeline interface.

What limitations exist when debugging Clojure apps with timeline recordings?▼

When debugging Clojure apps with timeline recordings, you must manually instrument namespaces and reload code before execution, meaning uninstrumented functions will not appear in the recorded flow data or timeline exploration.

Related Skills

Explore More Software Engineering Skills→
pyzepyze

clojure-mcp-repl

Execute Clojure and ClojureScript expressions via clojure-mcp for REPL-driven development.

Official
Intermediate
krzemienskikrzemienski
2

root-cause-tracing

Trace execution errors backward through call chains to identify root causes.

Community
Advanced
metabasemetabase
48.6k

clojure-write

Guides Clojure and ClojureScript REPL-driven development with small testable functions and namespace-based organization.

Official
Advanced
RamblurrRamblurr

scope-capture

Capture and inspect Clojure function local scope at runtime.

Community
Intermediate