dify-docs-format-check-en

Check English Markdown and MDX files against the Dify writing guide.

175|388|Updated Mar 11, 2025
One-click install
npx skills add https://github.com/langgenius/dify-docs --skill dify-docs-format-check-en
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dify-docs-format-check-en
Source: https://github.com/langgenius/dify-docs/tree/main/.claude/skills/dify-docs-format-check-en
Command: npx skills add https://github.com/langgenius/dify-docs --skill dify-docs-format-check-en

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify that English Dify documentation follows the repository's formatting rules before review or merge. It reduces manual style checking by combining an authoritative linter with a structured human review for issues that require judgment.

Core Features & Use Cases

  • Deterministic Format Auditing: Runs the English documentation linter against changed files and reports rule-based violations exactly as the script outputs them.
  • Judgment-Based Editorial Review: Checks headings, emphasis, lists, links, images, tables, and Mintlify component content for style issues that automation cannot reliably decide.
  • Change-Aware File Detection: Identifies relevant English Markdown and MDX files from unstaged, staged, and untracked changes, making it useful during final review of documentation updates.

Quick Start

Ask the skill to audit the changed English files and report both linter output and judgment-based formatting issues.

Frequently Asked Questions about dify-docs-format-check-en

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

FAQPage Schema
How do I check English MDX and Markdown formatting issues before merging documentation?

Documentation formatting checks identify changed .md and .mdx files under the en/ directory, running a bundled Python linter for deterministic rule violations and reviewing editorial style issues like headings and lists.

What is the best way to lint English documentation files against the Dify writing guide?

Linting English documentation against the Dify writing guide involves running the bundled Python linter to catch deterministic formatting errors, followed by a structured review of full files for judgment-based style issues that automation cannot reliably decide.

Does the documentation format checker modify Markdown files directly during review?

The documentation format checker does not modify files directly. It preserves the raw grouped linter output and reports formatting issues without altering your .md and .mdx files, ensuring a safe pre-merge audit process.

Can I use this editorial review tool for untracked and staged Git changes?

You can use this editorial review tool for untracked and staged changes. It detects relevant English Markdown and MDX files from unstaged, staged, and untracked Git changes, making it useful during documentation drafting and final pre-merge audits.

What documentation elements are checked during a judgment-based editorial review?

During a judgment-based editorial review, documentation elements like headings, emphasis, lists, links, images, tables, and Mintlify component content are checked for style issues that deterministic linter rules cannot reliably evaluate.