emacs-blog-reviewer

Name: emacs-blog-reviewer
Availability: InStock
Author: CaptainFlasmr

Identify technical issues in Emacs blog posts with category tags and fixes.

100|9|Updated Feb 6, 2025

Search Tags:#documentation #grammar #emacs #coding-standards #naming #elisp #blog-review

Ready to run

npx skills add https://github.com/captainflasmr/ollama-buddy --skill emacs-blog-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: emacs-blog-reviewer
Source: https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/emacs-blog-reviewer
Command: npx skills add https://github.com/captainflasmr/ollama-buddy --skill emacs-blog-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps editors verify Emacs blog posts for technical accuracy, naming conventions, and Emacs idioms, ensuring reliability for readers.

Core Features & Use Cases

Spelling, grammar, and punctuation checks tailored to Emacs terminology.
Verification of Emacs Lisp (Elisp) snippets for balanced parentheses, correct quoting, and valid syntax.
Validation of function/variable names, key bindings notation, and claims about built-in vs third-party packages.
Use Case: A technical writer publishes an Emacs-related blog post; this skill flags issues before publication.

Quick Start

Submit an Emacs blog draft to the reviewer and address all flagged issues.

Frequently Asked Questions about emacs-blog-reviewer

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

FAQPage Schema

How do I check Emacs blog posts for technical accuracy and naming inconsistencies?▼

To check Emacs blog posts for technical accuracy, you can use an automated reviewer to identify spelling, grammar, and naming inconsistencies. It validates Elisp snippets, key binding notations, and package claims, delivering a structured issue list with suggested fixes.

How do I verify Elisp code snippets and key binding notation in technical documentation?▼

Verifying Elisp code snippets and key binding notation in documentation involves checking balanced parentheses, correct quoting, valid syntax, and standard naming conventions. This process flags technical issues and outputs a structured list with exact quoted text and concise fixes.

Can I validate claims about built-in vs third-party Emacs packages in a draft?▼

Yes, you can validate claims about built-in vs third-party Emacs packages in a draft. The review process applies specifically to Emacs-related content, flagging incorrect package claims and historical Emacs API usage to ensure technical reliability for readers.

What is the best way to automate the review workflow for Emacs technical writing?▼

The best way to automate review workflows for Emacs technical writing is to submit the draft to a specialized reviewer. It flags spelling, grammar, and technical issues, returning a structured issue list with explicit category tags and suggested fixes suitable for automated processing.

Does Emacs blog review support checking historical Emacs API usage?▼

Yes, Emacs blog review supports checking historical Emacs API usage. It applies to Emacs-related content to identify outdated or incorrect API usage, alongside validating spelling, grammar, and Elisp syntax, providing a structured list of issues for correction.