skills/clojure-repl/SKILL.md
REPL-Driven Development Workflow in Clojure
npx skillsauth add abogoyavlensky/agents clojure-replInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run testing expression in the begining of a session JUST ONCE
brepl -e '(+ 1 2)'
3
If REPL is not running, that do not use this skill at all.
Run tests via command line with bb test, and clojure code if needed via clj -e
brepl -e '(user/run-tests)'brepl -e "(user/run-tests 'myproject.search-queries-test/test-preprocess-search-query-integration)"brepl -e '(user/run-tests "test/myproject/home_test.clj")Start by exploring small pieces of functionality in isolation:
; Try out simple expressions
brepl -e '(+ 1 2 3)'
6
; Explore and define data structures
brepl -e '(def sample-data [{:name "Alice" :score 42} {:name "Bob" :score 27} {:name "Charlie" :score 35}])'
#'user/sample-data
; REPL keeps state and definitions between your commands
; Try simple transformations
brepl -e '(map :score sample-data)'
(42 27 35)
tools
Run a second-opinion code review using the Codex CLI (`codex exec review`) in the background and surface the findings when it finishes. Use when the user says "review with codex", "second-opinion review", "what does codex think", or wants an outside model to look at local changes (uncommitted, current branch vs main, or a named commit). Also used as the review checkpoint inside the `executing-plans` skill.
documentation
Create structured implementation plan in docs/plans/
development
Review local code changes — uncommitted work, the current branch vs main, or a specific commit — for code quality, minimal implementation, basic security, and feature completeness. Use this skill whenever the user asks to review code, review changes, review a branch, review a commit, audit a diff, sanity-check what's about to be committed, or asks "is this ready to ship?" — even when they don't say the word "review" explicitly. This is a fast local review run inside the project, not the cloud-based /ultrareview. The output is a severity-grouped findings report with file:line citations.
testing
Use when writing prose humans will read - documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.