emacs-elisp-debugging

Diagnose Emacs Lisp syntax and compatibility failures in org-mode files.

Updated Mar 23, 2026

Search Tags:#debugging #emacs #literate programming #elisp #org-babel #paren errors

Ready to run

npx skills add https://github.com/luyangliuable/claude-setup --skill emacs-elisp-debugging-luyangliuable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: emacs-elisp-debugging
Source: https://github.com/luyangliuable/claude-setup/tree/main/.agents/skills/emacs-elisp-debugging
Command: npx skills add https://github.com/luyangliuable/claude-setup --skill emacs-elisp-debugging-luyangliuable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose and fix elusive Emacs Lisp failures, especially syntax problems like unmatched parentheses and compatibility issues between Common Lisp-style code and Emacs Lisp.

Core Features & Use Cases

Paren Error Isolation: Uses org-babel tangling bisection to narrow syntax mistakes in literate Emacs Lisp files.
Compatibility Debugging: Identifies Common Lisp constructs that need Emacs Lisp equivalents such as cl-lib forms and cl-return patterns.
Validation Workflow: Recommends check-parens, forward-sexp scanning, git diff comparison, and incremental testing to pinpoint failures.
Use Case: If a tangled .el file suddenly throws a wrong type argument or scan error, this Skill guides you to the exact faulty function or missing closing parenthesis.

Quick Start

Ask for help isolating the Emacs Lisp error in your org file and identify the smallest subtree or function that breaks tangling.

Frequently Asked Questions about emacs-elisp-debugging

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

FAQPage Schema

How do I debug Emacs Lisp paren errors in org-babel literate programming files?▼

To debug Emacs Lisp paren errors, apply org-babel tangling bisection to systematically narrow down syntax mistakes. Use check-parens validation and forward-sexp scanning to pinpoint unmatched parentheses in literate org-mode files.

Why does my tangled .el file throw a scan error or wrong type argument?▼

A tangled .el file throws a scan error or wrong type argument due to missing parentheses or Common Lisp versus Emacs Lisp mismatches. Use bisection and cl-lib-aware corrections to identify the exact faulty function.

What is the best way to fix Common Lisp compatibility issues in Emacs Lisp?▼

The best way to fix Common Lisp compatibility issues in Emacs Lisp is to identify Common Lisp constructs that require Emacs Lisp equivalents. Apply cl-lib-aware corrections, replacing outdated patterns with cl-lib forms and cl-return patterns.

How to validate Emacs Lisp buffers for malformed nested forms in batch mode?▼

Validate Emacs Lisp buffers for malformed nested forms in batch mode by running check-parens validation, performing forward-sexp scanning, and comparing git diffs. Incremental testing isolates syntax failures reliably.

Can I isolate a missing closing parenthesis without running the entire Emacs Lisp file?▼

Yes, you can isolate a missing closing parenthesis without running an entire Emacs Lisp file by requesting org-babel tangling bisection. This isolates the smallest subtree or function that breaks tangling.