Fix byte-compile warnings, checkdoc notes, and other Elisp diagnostics in one or more files. Use when the user says "lint elisp", "fix warnings", "fix diagnostics", "elisp lint", "checkdoc", "byte-compile warnings", or wants to clean up Elisp compiler/linter output.
Relocate Claude Code internal session logs, not Codex logs, and rewrite the embedded paths so resume keeps working. Two modes — single session (move one .jsonl from another project to the current project) and whole-project rename (move all sessions when a project directory has been renamed). Use when the user says…
Coordinate a two-agent planner/reviewer loop across live Emacs agent sessions. Use when the user asks to orchestrate Claude/Fable and Codex, run paired model review, converge a plan through back-and-forth review, monitor agent sessions until completion, or make a multi-agent review process unattended.
Use when creating or editing an org-mode note file. Applies note-structure and prose-formatting conventions for private or personal Org notes, regardless of directory.
Batch-process org-roam TODOs autonomously. Acts on TODOs that can be completed without user input and records blockers for the rest, sorted by ease of unblock. Use when the user says "overnight todos", "run overnight", "process my todos", "todo batch", "act on my todos", or schedules a nightly run.
Draft in Pablo's own voice anything he will send or publish as himself — email, Slack, forum/PR comments, tweets, Google Docs/Sheets comments, letters, reviews. Use whenever composing text that will go out under Pablo's name, even a one-line reply or a quick DM. It matches his private voice samples AND avoids…
Pin an Emacs/Elpaca package in dotfiles to a fork, branch, or upstream PR while it awaits merge. Use when the user asks to use their fork, pin a package to a PR branch, temporarily install an Elisp package from a fork, or keep an upstream fix active in emacs/config.org. Enforces one package, one recipe: modify or move…
Close the loop after agent pushes by waiting for GitHub Actions, inspecting failed logs, fixing push-triggered CI failures, and repeating until the pushed commit is green or a real blocker is identified. Use whenever an agent pushes commits or the user asks to check CI after a push.
Verify a PR or PR-ready branch before submitting, pushing, merging, or after revision. Runs build/test checks, commit review, upstream alignment, file hygiene, and remote CI checks when available.
Proofread Markdown for spelling, grammar, typos, punctuation, and light style/clarity issues. Use for proofread, spell check, grammar check, typo review, or proofreading a Markdown file.
Extract and record architectural, algorithmic, or design decisions from the current session. Use at the end of a session (usually via /update-log), when the user asks to record/capture an ADR or decision, or when a significant trade-off was made.
Rebuild and republish the CR-task master tracker artifact. Use when the user says "refresh cr tracker", "update the CR task tracker", "/refresh-cr-tracker", or wants the conceptual-reasoning task master list re-pulled from live reasoning-tasks data + GitHub issues and redeployed to its claude.ai artifact.
Release one of the user's Emacs packages or audit package release readiness. Use when the user says /release-package , asks to bump/tag/create a GitHub release, wants release notes for a benthamite Emacs package, or runs /release-package --audit; do not use for dotfiles releases.
Review the current session when a Stop/session-end hook asks for lesson capture, then write candidate reusable lessons and promotion metadata to the central dotfiles .agent-learnings/inbox without implementing them. Use when a hook prompt says to capture session lessons, review current-session learnings, populate the…
Run an invariant-focused root-cause check before a non-trivial bug fix. Use after initial debugging when a local patch is tempting; not for trivial typo/formatting fixes or greenfield features.
Create or expand high-value test suites for a codebase or specific module. Use when the user asks to add or write tests, improve coverage, bootstrap testing, create regression tests, or test a module/codebase; not for ordinary bug-fixing unless tests are the requested deliverable.
End-of-session bookkeeping. Do NOT invoke this on your own initiative, and do NOT hand-write a session log yourself instead of invoking it — writing or editing any file under a project's logs/ directory is this skill's job alone. Run it only when the user explicitly asks (the user types /update-log or says update log…
Run an explicit user-requested verification loop. Use when the user asks to verify, close the loop, define success criteria, or rigorously check non-code outputs; not for routine coding completion or narrower audit/debug checks.
Diagnose a frozen, hung, beachballing, or unresponsive Emacs by sampling the process, reading server buffers when possible, and recommending recovery. Use when Emacs is stuck or not responding; do not use for ordinary Elisp errors while Emacs is responsive.
Run post-Emacs-profile-switch housekeeping after elpaca profile changes. Use when the user says "/migrate-profile", changes Emacs or elpaca profiles, switches to a new profile, or wants Claude/Codex sessions, memory, trust entries, history, cwd paths, profile symlinks/caches, or new-profile repos checked after a…
Rename an Emacs package end to end, especially elpaca-managed standalone packages. Use when the user asks to rename a package, local files, feature/symbol prefixes, GitHub repository, elpaca source directory, or references in dotfiles/system configuration.
Audit a macOS .app before running it or granting permissions, especially when the user asks whether a Mac app is safe, suspicious, malware, from an unknown developer, or requests screen recording, accessibility, camera, microphone, input monitoring, or other sensitive permissions.
Use when a LuLu firewall alert is open on this Mac and the user asks whether to allow or block it, or asks to inspect, check, audit, or review the connection a LuLu alert is prompting about. Covers explicit $review-lulu-alert requests and questions like "should I allow this?", "what is this process connecting to?", or…
Scan for exposed API keys and leaked credentials, audit dependency vulnerabilities, review macOS hardening settings, and evaluate Claude Code configuration risks. Use when the user wants a security review, vulnerability scan, dependency audit, secrets check, or periodic security posture assessment.
★not rated 11 1mo agoB55 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: