clojure-syntax-rescue

Identify and repair unmatched delimiters and EOF errors in Clojure source code.

6|Updated Mar 11, 2026

Search Tags:#debugging #syntax #clojure #linter #brackets #macro #eof

Ready to run

npx skills add https://github.com/open-hax/opencode-skills --skill clojure-syntax-rescue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clojure-syntax-rescue
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/clojure-syntax-rescue
Command: npx skills add https://github.com/open-hax/opencode-skills --skill clojure-syntax-rescue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protocol to recover from Clojure/Script syntax errors, specifically bracket mismatches and EOF errors.

Core Features & Use Cases

Identify exact line/column of mismatches using clj-kondo or pnpm lint.
Isolate the top-level form containing the error to simplify debugging.
Check macros and threading constructs to avoid nested issues.
Verify with a linter to ensure a syntactically valid result.

Quick Start

Provide the faulty Clojure file to the Clojure Syntax Rescue skill and let it guide you to locate the mismatch, isolate the top-level form, and correct brackets to produce a syntactically valid file.

Frequently Asked Questions about clojure-syntax-rescue

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

FAQPage Schema

How do I fix unmatched delimiters and EOF errors in Clojure source code?▼

To fix unmatched delimiters and EOF errors in Clojure source code, you need to identify the exact line and column of mismatches using a linter. Isolate the top-level form containing the error to simplify debugging and correct the brackets for a syntactically valid file.

What is the best way to debug bracket mismatches in complex nested Clojure macros?▼

The best way to debug bracket mismatches in nested Clojure macros is to isolate the top-level form containing the error. By checking macros and threading constructs separately, you avoid nested issues and can verify the syntax with a linter.

Can I use clj-kondo to locate syntax errors in multi-level top-level forms?▼

Yes, you can use clj-kondo to locate syntax errors in multi-level top-level forms. The linter identifies the exact line and column of bracket mismatches, allowing you to isolate the faulty form and verify the corrected result.

How do I isolate a top-level form to troubleshoot Clojure syntax errors?▼

To isolate a top-level form and troubleshoot Clojure syntax errors, locate the mismatch using a linter, then separate the problematic top-level form from the rest of the file. This simplifies debugging complex nested macros and threading constructs.

Why does my Clojure linter report an EOF error on a valid-looking form?▼

Your Clojure linter reports an EOF error because of an unmatched delimiter hidden within complex forms or nested macros. Isolate the top-level form, check the threading constructs, and correct the brackets to resolve the unexpected end of file.