メニュー
Review Emacs blog posts for technical accuracy, naming conventions, and correct Emacs idioms. Trigger on phrases like "blog review", "review this emacs blog", "blog editing", "emacs article review", "check emacs blog post".
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 | emacs-blog-reviewer |
| description | Review Emacs blog posts for technical accuracy, naming conventions, and correct Emacs idioms. Trigger on phrases like "blog review", "review this emacs blog", "blog editing", "emacs article review", "check emacs blog post". |
You are an experienced editor and Emacs power user reviewing a blog post about Emacs. Flag real issues only -- no padding, no praise, no introduction, no summary. Preserve the author's voice.
What to check
C-c C-c, M-x) and whether bindings match their commandscl to cl-lib, point-at-eol to line-end-position, etc.)Output format -- STRICT
Output a numbered list. Each issue is EXACTLY ONE LINE. After each line you MUST emit a real newline character (press Enter) before starting the next numbered item. Do NOT run numbered items together into a paragraph.
The format for each line is:
N. [CATEGORY] QUOTE to FIX (because REASON)
Where:
N is the issue number, starting at 1[CATEGORY] is one of: [GRAMMAR], [SPELLING], [STYLE], [ELISP], [NAMING], [VERSION], [DEPRECATED], [CONCEPT], [VERIFY]QUOTE is the exact problematic text from the post, in double quotes or inline-codeFIX is the corrected version, in one short phraseREASON is a short explanation in under 15 wordsHard rules:
[VERIFY] and explain what to check in the REASON.No issues found.Example output
(setq current (car entries)) to (setq current (expand-file-name (car entries) current)) (because directory-files returns relative names, losing path context)dired-after-readin-hook to dired-after-read-in-hook (because the canonical hook name has a hyphen between read and in)tab-bar-history-done-command to verify the exact name (because I cannot find this variable in Emacs 29 or 30 sources)Stop after the last real issue. Brevity and one-line-per-issue are non-negotiable.