editor

Analyze documentation text for grammar, style, and factual accuracy.

7|3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/Norman-Norman-Norman/customize-your-repo --skill editor-norman-norman-norman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editor
Source: https://github.com/Norman-Norman-Norman/customize-your-repo/tree/main/.github/skills/editor
Command: npx skills add https://github.com/Norman-Norman-Norman/customize-your-repo --skill editor-norman-norman-norman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces the risk of publishing low-quality documentation by automatically reviewing text for grammar, clarity, consistency, and factual accuracy. It helps teams catch issues before release and during PR reviews.

Core Features & Use Cases

  • Grammar and style checks across documentation files to ensure readability and correctness
  • Terminology consistency enforcement across a project to maintain a unified voice
  • Link validation and cross-reference checks to prevent broken references
  • Pre-commit or PR review assistance that surfaces issues and suggested fixes

Quick Start

Run the editor on modified docs, for example: editor.review docs/README.md

Frequently Asked Questions about editor

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

FAQPage Schema
How do I automate proofreading and grammar checks for documentation files?

Automated proofreading for documentation files is achieved by analyzing text for grammar, style, and factual accuracy. This skill surfaces issues like grammar errors and inconsistent terminology, applying built-in rules and project-specific guidelines to ensure readability and correctness.

Can I enforce terminology consistency across my project documentation?

Yes, terminology consistency is enforced across project documentation to maintain a unified voice. The review process identifies inconsistent terminology and suggests corrections based on your defined project-specific guidelines and built-in style rules.

What's the best way to validate links and cross-references in docs before publication?

Validating links and cross-references before publication is handled through automated checks that prevent broken references. The review process scans documentation files to identify and surface broken links, ensuring all references remain accurate and functional.

How do I run editorial reviews on modified docs during a PR review?

Running editorial reviews during a PR review is supported by executing the review command on modified documentation files. This pre-commit or PR review assistance surfaces identified issues and provides suggested fixes directly within your workflow.

Does this editorial review process support project-specific style guidelines?

Yes, the editorial review process supports project-specific style guidelines alongside built-in rules. It analyzes documentation text for style conformance, ensuring that your project maintains its required voice and formatting standards before release.