emacs-literate-programming

Tangle .org Emacs configuration sources into generated .el files.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/moogah/emacs --skill emacs-literate-programming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emacs-literate-programming
Source: https://github.com/moogah/emacs/tree/main/.claude/skills/emacs-literate-programming
Command: npx skills add https://github.com/moogah/emacs --skill emacs-literate-programming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Editing Emacs configuration directly in generated .el files leads to drift and overwrites. This skill enforces literate programming by treating .org sources as the canonical representation and tangling to .el files.

Core Features & Use Cases

  • Keeps .org sources as the single source of truth for Emacs configuration
  • Supports automatic tangling when saving and manual tangling when needed
  • Prevents unintended edits to generated .el files and promotes reproducible configurations
  • Use Case: When updating your Emacs config in emacs/ directory, tangle changes to emit updated .el version automatically

Quick Start

Edit the Emacs Lisp configuration in the emacs/ directory via .org sources and trigger tangling.

Frequently Asked Questions about emacs-literate-programming

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

FAQPage Schema
How do I keep Emacs configuration in org-mode from drifting from generated elisp files?

Treat .org source files as the canonical representation of your Emacs configuration and tangle changes into corresponding .el files. This prevents manual edits to generated elisp code and ensures reproducible configurations.

What is automatic tangling for Emacs literate programming and how does it work?

Automatic tangling compiles embedded Emacs Lisp code blocks within .org files into .el files upon saving. It enforces a literate programming workflow by maintaining .org sources as the single source of truth.

How do I update my Emacs config using org-mode and elisp tangling?

Edit the Emacs Lisp configuration in your emacs/ directory via .org sources and trigger tangling. Saving the .org file emits an updated .el version automatically when auto_tangle is enabled.

Do I need auto_tangle enabled to manage Emacs configuration with org-mode?

You need a literate programming workflow with automatic tangling enabled, such as auto_tangle, and a clear separation between source .org and generated .el artifacts to use this workflow effectively.

Why should I use org-mode for Emacs config management instead of editing elisp directly?

Editing generated .el files directly leads to drift and overwrites. Using org-mode sources as the canonical representation promotes reproducible configurations and prevents unintended edits to generated code.

What are the limitations of using org-mode tangling for Emacs configuration?

This workflow requires a clear separation between source .org and generated .el artifacts. It is not suitable if you need to manually edit generated .el files, as tangling will overwrite manual changes.