Clojure REPL Evaluation Skill

Evaluate Clojure code through nREPL with session persistence and timeout flags.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/brianium/sfere --skill clojure-repl-evaluation-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Clojure REPL Evaluation Skill
Source: https://github.com/brianium/sfere/tree/main/.claude/skills/clojure-eval
Command: npx skills add https://github.com/brianium/sfere --skill clojure-repl-evaluation-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly verify that Clojure code compiles, loads, and behaves as expected by running it in a persistent nREPL-backed REPL session instead of guessing from static edits.

Core Features & Use Cases

  • Interactive nREPL evaluation: Run expressions against a selected nREPL server and get immediate results, including for quick arithmetic or business logic checks.
  • Namespace loading with :reload: Re-require namespaces using :reload so the latest code changes are exercised without restarting the session.
  • Session management for repeatable debugging: Persist state across evaluations and optionally reset the session if earlier interactions cause confusing results.

Quick Start

Run: clj-nrepl-eval -p <PORT> "(require '[ascolais.sfere :as sfere] :reload)" to load the latest version of the namespace in your current session.

Frequently Asked Questions about Clojure REPL Evaluation Skill

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

FAQPage Schema
How do I evaluate Clojure code in a live nREPL session?

You can evaluate Clojure code by running expressions against a selected nREPL server port to validate compilation and behavior, using provided evaluation flags to manage timeout and optional session resets.

How do I reload Clojure namespaces without restarting my REPL session?

To reload namespaces without restarting your REPL session, use the :reload flag with the require expression in your nREPL evaluation to exercise the latest code changes in the persistent session.

Can I persist state across multiple Clojure REPL evaluations?

Yes, you can persist state across multiple Clojure REPL evaluations using session management, which maintains your environment for repeatable debugging and optionally resets if earlier interactions cause confusing results.

Do I need to specify a port to connect to a Clojure nREPL server?

You can target an explicit port for Clojure nREPL evaluation, or rely on server discovery if available, ensuring the command line tooling connects to the correct live development session.

What are the limitations of using an nREPL evaluation session for debugging?

Limitations of nREPL evaluation include potential confusing results from earlier interactions, requiring an optional session reset, and the need to manage timeouts using provided evaluation flags during multi-step test expressions.