Review Markdown files or PR changes for reader-focused documentation issues.
npx skills add https://github.com/umbraco/UmbracoDocs --skill review-docs-umbraco
Please help me install this Agent Skill. Skill: review-docs Source: https://github.com/umbraco/UmbracoDocs/tree/main/.claude/skills/review-docs Command: npx skills add https://github.com/umbraco/UmbracoDocs --skill review-docs-umbraco
Review documentation from the reader's perspective, surfacing unclear sections, fluff, missing context, and maintenance burden to improve usability.
Provide one or more file paths or 'pr' to run a review in file mode or PR mode.
High-intent search queries and answers about installing and using this skill.
Review Markdown documentation by analyzing it from a reader's perspective, surfacing unclear sections, fluff, and missing context. This process evaluates reader value, clarity, completeness, maintainability, and factual accuracy to improve overall usability.
Review all changed Markdown files in a PR by running the tool in PR mode. This compares the current branch to main, automatically running Vale linting and link checking before analyzing the documentation for reader-focused quality improvements.
Automate documentation quality assurance in a pull request by triggering PR mode to evaluate changed Markdown files. The workflow integrates Vale linting and link checking, enforcing reader value, clarity, completeness, maintainability, and factual accuracy across the modifications.
Yes, you can review a single Markdown file by providing its path to run the tool in file mode. This allows you to analyze an individual open file or specific document path for reader-focused quality issues and improvement opportunities.
Yes, documentation linting checks for broken links and readability issues using Vale linting and link checking. These automated checks surface maintenance burdens and unclear sections before analyzing the documentation for reader value, clarity, and factual accuracy.
Reviewing documentation from a reader's perspective goes beyond formatting to surface missing context, fluff, and maintenance burden. It enforces evaluation across reader value, clarity, completeness, maintainability, and factual accuracy, ensuring the documentation genuinely improves usability.
erclxSynchronize README and markdown documentation by rewriting stale sections from git diffs.
nickmaglowschGenerates a Markdown PR description from task files and git diff.
AJBcodingLint Markdown documentation for formatting, broken references, and structural issues.
georgekhananaevEnforce consistent Markdown syntax across documentation and README files.
