elisp-review

To check Emacs Lisp code quality before release, run a structured static analysis review on your .el files to identify lexical-binding issues, enforce cl-lib usage, and validate provide/require statements. This surfaces undefined functions and defcustom metadata issues for actionable remediation.

Auditing legacy Emacs Lisp libraries for modern API usage involves a semantic review process that checks for consistent API patterns, proper cl-lib adoption, and robust error handling. This structured review ensures public functions meet documentation quality standards and compatibility requirements.

Byte-compilation checks for Emacs Lisp static analysis work by running batch processing on target files to surface undefined functions, wrong argument counts, and defcustom issues. This phase identifies runtime risks that static pattern matching alone might miss during code review.

You can validate lexical-binding and defcustom metadata in Elisp scripts through static pattern checks designed for Emacs Lisp codebases. These checks enforce proper provide/require usage and ensure defcustom definitions include required metadata for package compatibility.

Your Emacs Lisp review reports undefined functions during batch checks because the byte-compilation phase identifies missing function definitions and incorrect argument counts across target .el files. This surfaces potential runtime errors requiring remediation before package release or deployment.

Yes, elisp-review operates without external dependencies or components, running static analysis and semantic reviews directly on target Emacs Lisp files. This allows you to perform code audits and generate remediation guidance without installing additional packages or configuring complex environments.