docs-writer

Enforce documentation standards across Markdown files and the /docs directory.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/liuning0820/skills --skill docs-writer-liuning0820
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-writer
Source: https://github.com/liuning0820/skills/tree/main/skills/docs-writer
Command: npx skills add https://github.com/liuning0820/skills --skill docs-writer-liuning0820

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often fails to meet consistency, tone, and formatting standards, leading to confusion and inconsistent user experience. This skill ensures accurate, clear, and uniform documentation during writing, editing, or reviewing tasks.

Core Features & Use Cases

  • Enforces project documentation standards including voice, tone, grammar, and formatting.
  • Guides editing tasks to align with CONTRIBUTING.md and established style guides.
  • Ensures consistency across the /docs directory and Markdown files with review workflows.

Quick Start

Provide a markdown document and request a standards-compliant rewrite.

Frequently Asked Questions about docs-writer

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

FAQPage Schema
How do I enforce documentation standards across a repository's markdown files?

To enforce documentation standards, apply the skill to the /docs directory and all Markdown files to ensure voice, tone, grammar, and formatting consistency. It satisfies Phase 1-4 guidelines with audit-ready processes.

How do I check markdown formatting consistency in a /docs directory?

Check markdown formatting consistency by running review workflows against the /docs directory. This enforces tone, structure, and formatting checks to ensure accurate, clear, and uniform documentation.

What is the best way to align markdown editing tasks with a CONTRIBUTING.md style guide?

Align markdown editing tasks with a CONTRIBUTING.md style guide by guiding edits to match established voice and formatting rules. This ensures accurate, clear, and uniform documentation during writing or reviewing.

Can I apply voice and tone standards to existing markdown documents?

Apply voice and tone standards to existing markdown documents by providing the markdown document and requesting a standards-compliant rewrite. This enforces project documentation standards including tone, structure, and consistency.

Does this documentation editing workflow satisfy Phase 1-4 guidelines?

This documentation editing workflow satisfies Phase 1-4 guidelines by enforcing tone, structure, and consistency checks. It applies audit-ready processes to the /docs directory and all Markdown files.

Why does my repository documentation fail tone and formatting consistency checks?

Repository documentation fails tone and formatting consistency checks when it does not align with established style guides. Enforcing project documentation standards during writing and editing resolves this confusion.