EmacsLisp

Publishing to MELPA requires a package with proper headers, lexical-binding declaration, and passing package-lint checks. Use Eask to automate builds and testing, then submit your repository to MELPA's GitHub. The Skill covers the full workflow including header conventions, native compilation readiness, and MELPA submission pipelines.

ERT (Emacs Lisp Regression Testing) is the standard framework for testing Emacs Lisp packages. Write test cases using ERT's assertion macros, run them with your build tool, and integrate checks into your CI pipeline. This Skill provides guidance on structuring ERT-based test suites and linting with package-lint and checkdoc.

Configure your init file with proper conventions, enable lexical-binding in your source files, and use Eask for dependency management and build automation. This Skill covers Emacs configuration best practices, native compilation readiness, and tooling setup for package development workflows.

Yes. MELPA accepts any package meeting technical standards, while GNU ELPA and NonGNU ELPA have stricter requirements and licensing rules. This Skill documents publishing workflows for all three repositories, including how to prepare releases and meet each platform's specific header and documentation conventions.

Package headers declare metadata like version, dependencies, and description using standardized conventions. They enable proper parsing by package managers and are validated by package-lint and checkdoc. This Skill covers header structure, lexical-binding declarations, and native compilation markers required for modern package publishing.

Use package-lint to check metadata and conventions, and checkdoc to validate documentation strings. Both tools catch common mistakes before publishing. This Skill integrates these linters into development workflows via Eask, ensuring compliance with MELPA and ELPA submission standards.