skills.rest
captainflasmr
captainflasmrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

package-developer-guide

Guide Emacs developers in creating MELPA/ELPA submission-ready packages.

100|9|Updated Feb 6, 2025
Search Tags:#testing#documentation#emacs#packaging#melpa#elpa#package-development
One-click install
npx skills add https://github.com/captainflasmr/ollama-buddy --skill package-developer-guide
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: package-developer-guide
Source: https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/package-developer-guide
Command: npx skills add https://github.com/captainflasmr/ollama-buddy --skill package-developer-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain high-quality Emacs packages that meet MELPA/ELPA submission standards, ensuring developers follow community guidelines and pass reviews.

Core Features & Use Cases

  • Guidance on proper namespace conventions and prefix usage for reliable package branding.
  • Documentation, testing strategies (ERT, Buttercup), and packaging requirements to prepare and maintain submission-ready packages.
  • Use cases include starting a new package, organizing project structure, and keeping dependencies in harmony with Emacs ecosystem.

Quick Start

Scaffold a new Emacs package project following MELPA/ELPA guidelines and configure namespace, autoloads, and basic tests.

Frequently Asked Questions about package-developer-guide

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

FAQPage Schema
How do I prepare an Emacs package for MELPA submission?▼

To prepare an Emacs package for MELPA submission, follow community guidelines for proper namespace prefixes, autoload handling, dependency management, and testing strategies to ensure your package passes reviews.

What is the correct namespace prefix convention for Emacs package development?▼

Emacs package development requires proper namespace prefixes to ensure reliable package branding and prevent function name conflicts across the ecosystem. Consistent prefix usage is essential for MELPA and ELPA compatibility.

How do I set up testing for an Emacs package using ERT and Buttercup?▼

Setting up testing for an Emacs package involves configuring ERT and Buttercup testing strategies within your project structure. This ensures your package meets submission-ready quality standards for the Emacs ecosystem.

Can I scaffold a new Emacs package project to meet ELPA standards?▼

Yes, you can scaffold a new Emacs package project following MELPA and ELPA guidelines. This includes configuring namespaces, autoloads, defcustom configurations, and basic tests for small to mid-sized projects.

What should I include in Emacs package documentation for MELPA reviews?▼

Emacs package documentation for MELPA reviews should include proper defcustom configurations, dependency management details, and clear usage instructions. Comprehensive documentation is required to pass community submission reviews.

Related Skills

Explore More Software Engineering Skills→
KyonaxKyonax

emacs-expert

Test Emacs Lisp code in the Doom Scratch Buffer before config integration.

Community
Intermediate
hugoduncanhugoduncan
3

ert

Run ERT tests for Emacs Lisp with assertions and batch mode.

Community
Advanced
captainflasmrcaptainflasmr
100

elisp-project-management-expert

Guide Emacs Lisp project structure, dependencies, and packaging workflows.

Community
Advanced
plurigridplurigrid
60

proofgeneral-narya

Bridge Proof General and Narya for version-controlling higher-dimensional type-theory proofs.

Official
Advanced