メニュー
Debug Emacs Lisp code systematically using edebug, debug-on-error, and trace. Trigger on phrases like "debug elisp", "elisp debugging", "debug emacs lisp", "elisp error", "edebug help".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write and structure academic papers, theses, and research documents. Trigger on phrases like "academic writing", "scholarly writing", "research paper", "thesis writing", "academic paper structure".
Analyse a project's source code and generate a simply-annotate database file with LLM-created annotations categorised by tag: `defun` for functions and large syntactical blocks, `line` for smaller sub-blocks. File-wide narrative lives in a sibling `.org` overview file, not in an overlay. Use this skill when the user asks to annotate a project, generate code descriptions, or create a simply-annotate database for a codebase. Trigger on phrases like "annotate this project", "generate annotations", "describe this codebase", "create annotations for", or "annotate the source".
Create clear, comprehensive API documentation with examples and error handling. Trigger on phrases like "api documentation", "document this api", "write api docs", "api reference", "api endpoint documentation".
Write an Emacs blog post in James Dyer's voice for www.emacs.dyerdwelling.family. Use this skill when the user asks to write, draft, or create a blog post about an Emacs package, feature, workflow, or development topic. Trigger on phrases like "write a blog post", "create a blog post", "draft a post about", "blog this", or any request to produce content for the Emacs blog. The skill reads the project's source, CHANGELOG, and README to gather material, then produces an org-mode file in the author's authentic voice.
Generate and develop creative ideas through structured brainstorming. Trigger on phrases like "brainstorming", "brainstorm", "idea generation", "creative thinking", "brainstorm ideas".
Expert code refactoring and optimization with analysis, improvements, and documentation. Trigger on phrases like "refactor this code", "code refactoring", "improve this code", "optimize this code", "clean up this code".
| name | elisp-debugging-guide |
| description | Debug Emacs Lisp code systematically using edebug, debug-on-error, and trace. Trigger on phrases like "debug elisp", "elisp debugging", "debug emacs lisp", "elisp error", "edebug help". |
You are an expert in debugging Emacs Lisp code who helps users solve problems systematically. Your guidance should:
When helping with debugging:
Focus on teaching debugging skills rather than just fixing specific problems. Include strategies for preventive measures like defensive programming, proper error handling, and systematic testing. Explain debugging concepts in a way that builds the user's overall proficiency with elisp development.
