How does the Documentation Review skill handle GitHub PRs?

It uses GitHub MCP tools to create a pending review, batching all identified issues into parallel comments on specific lines to avoid notification fatigue.

What formatting rules does it prioritize?

It specifically looks for proper UI element bolding, descriptive link text instead of 'click here', and the removal of qualifiers like 'just' or 'simple'.

Why does it number every issue sequentially?

Sequential numbering is a mandatory requirement that allows developers and writers to reference specific feedback points (e.g., 'Fix issue 3') for faster iterations.

Does this skill work with any style guide?

While it is specifically pre-configured for the Metabase writing style guide, its core logic covers universal best practices for clear, accessible technical documentation.

Documentation Style Reviewer

Name: Documentation Style Reviewer
Author: Microck

byMicrock

•

Learning & Documentation

Audits Markdown documentation for style guide compliance and clarity within local environments or GitHub pull requests.

About

The Documentation Style Reviewer is a specialized skill designed to automate the technical editing process by enforcing the Metabase writing style guide. It intelligently detects its environment to either provide a numbered list of issues in a local chat or post structured comments directly onto a GitHub Pull Request. The skill focuses on improving tone, structure, and formatting—such as ensuring UI elements are bolded rather than backticked—while filtering out trivial suggestions to focus on material improvements that enhance reader comprehension.

Key Features

Sequential issue numbering for easy referencing in team discussions
81 GitHub stars
Formatting validation for UI elements, links, and code snippets
Tone and voice analysis to eliminate corporate jargon and condescending language
Dual-mode operation for both local CLI and GitHub PR environments
Automated style guide compliance checking for Markdown files

Use Cases

Ensuring technical writers maintain a consistent conversational tone across large projects
Automating the first pass of documentation reviews in GitHub Pull Requests
Quickly scanning new Markdown content for common formatting errors before publication

About

Key Features

Sequential issue numbering for easy referencing in team discussions
81 GitHub stars
Formatting validation for UI elements, links, and code snippets
Tone and voice analysis to eliminate corporate jargon and condescending language
Dual-mode operation for both local CLI and GitHub PR environments
Automated style guide compliance checking for Markdown files

Use Cases

Ensuring technical writers maintain a consistent conversational tone across large projects
Automating the first pass of documentation reviews in GitHub Pull Requests
Quickly scanning new Markdown content for common formatting errors before publication