Review documentation changes against a specified writing style guide.
npx skills add https://github.com/Palomig/PALOMATIKA --skill docs-review-palomig
Please help me install this Agent Skill. Skill: docs-review Source: https://github.com/Palomig/PALOMATIKA/tree/main/.claude/skills/docs-review Command: npx skills add https://github.com/Palomig/PALOMATIKA --skill docs-review-palomig
This Skill addresses the challenge of maintaining high-quality, consistent documentation by automatically reviewing changes against a defined style guide, ensuring clarity, adherence to tone, and proper formatting.
Review the provided documentation changes for compliance with the Metabase writing style guide.
High-intent search queries and answers about installing and using this skill.
To review documentation changes for style guide compliance, provide the updated markdown files or pull request diffs alongside your specified writing style guide. The review identifies deviations in tone, voice, structure, clarity, links, and formatting.
Enforcing a writing style guide in a pull request involves comparing the documentation diffs against defined rules for tone, voice, and formatting. This process flags verbose text, vague headings, unclear instructions, and improper link text for the author to correct.
Checking markdown formatting and link text during a documentation audit requires comparing files against your style guide rules. This identifies inconsistent list formatting, improper link text, and structural deviations to ensure content quality and consistency.
Yes, a documentation review requires access to the specified style guide document to compare changes against established rules. Without the style guide, the review cannot evaluate tone, voice, clarity, or formatting compliance.
Yes, you can use this documentation review for both local audits and pull request reviews. It processes provided file changes and diffs to identify style guide deviations, ensuring content quality across different review workflows.
mwathibenIdentify style violations in documentation diffs against the Metabase writing style guide.
Yeachan-HeoEvaluate plan files in .omx/plans/ with Critic-based review verdicts.
kryptobaseddevReview Markdown documentation for CLEO style compliance with inline comments.
iAmAdheilConvert markdown content into interactive HTML documents with CSS formatting.
