Menu
Run doom sync after config changes and diagnose any errors
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add a new Emacs package to this doom config — packages.el declaration, config.org section, and doom sync
Run static analysis and byte-compile checks on the Doom config without opening Emacs
Systematically debug a doom emacs issue — errors, broken packages, slow startup, keybinding conflicts
Look up a Doom Emacs module's documentation, flags, and packages before configuring anything manually. Use this when the user asks about adding a feature, package, or integration to Doom.
Update doom emacs and/or packages — runs doom upgrade, handles errors, summarizes what changed
Expert Emacs Lisp programmer and Doom Emacs architect. Use when writing custom packages, configuring complex behaviors, debugging elisp, designing abstractions, or any task that requires deep Emacs/Doom knowledge.
| name | doom-sync |
| description | Run doom sync after config changes and diagnose any errors |
| argument-hint | [-- flags] |
| allowed-tools | Bash, Read, Grep |
Run doom sync to apply pending config changes and handle the output.
Run doom sync:
~/.config/emacs/bin/doom sync $ARGUMENTS 2>&1
Inspect the output:
On error, check:
packages.el? Grep config.org and packages.el for the package name.:recipe for non-MELPA packages?init.el vs config.org usage?doom doctor to surface environment issues: ~/.config/emacs/bin/doom doctor 2>&1 | head -80After a successful sync, remind the user to:
M-x doom/reload inside Emacsdoom sync --rebuild~/.config/emacs/bin/doom~/.config/emacs/.local/straight/build-*/~/.config/emacs/eln-cache/