golem

Audit documentation style, grammar, and terminology across project files.

8|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/smile13241324/aemacs --skill golem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem
Source: https://github.com/smile13241324/aemacs/tree/main/.agents/skills/golem
Command: npx skills add https://github.com/smile13241324/aemacs --skill golem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The golem solves the need to maintain consistent, clear, and well-structured project documentation and code comments across teams.

Core Features & Use Cases

  • Review and enforce documentation style, grammar, and terminology across READMEs, inline comments, and design docs.
  • Suggest consistency improvements and provide guidelines aligned with project standards.
  • Use case: A software team standardizes all documentation to reduce ambiguity and accelerate onboarding.

Quick Start

Run the doc review pass on the repository to generate a style report and suggested edits.

Frequently Asked Questions about golem

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

FAQPage Schema
How do I check and enforce documentation consistency across my project?

To enforce documentation consistency, run an audit pass on your repository to generate a style report with suggested edits. This reviews READMEs, inline comments, and design docs to align grammar, terminology, and structure with project style guides.

What is the best way to standardize README and inline code comments for a team?

The best way to standardize READMEs and inline comments is to run an automated documentation review pass. It enforces stylistic consistency, checks terminology, and provides guidelines aligned with your project standards to reduce ambiguity.

Can I use this to audit design docs and project documents across different formats?

Yes, you can audit design docs and project documents across languages and formats. The documentation review applies grammatical rules, structural checks, and terminology enforcement to ensure clarity and consistency throughout your repository.

How does terminology and grammar enforcement work for project documentation?

Terminology and grammar enforcement works by scanning your project documents and inline comments against established style guidelines. It then outputs a style report detailing inconsistencies and suggesting edits to accelerate team onboarding.

Do I need a specific style guide to review and improve project documentation?

No specific external style guide is required as a dependency to review and improve project documentation. The tool audits your existing documents and suggests consistency improvements aligned with the project standards you already have.

Why does my repository documentation have inconsistent grammar and structure?

Inconsistent grammar and structure occur when project documents lack automated enforcement. Running a doc review pass on your repository generates a style report with suggested edits to align terminology and enforce structural consistency across files.