woocommerce-markdown

Lint WooCommerce Markdown files against configured markdownlint rules.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/mwathiben/PropManager --skill woocommerce-markdown-mwathiben
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: woocommerce-markdown
Source: https://github.com/mwathiben/PropManager/tree/main/.claude/skills/woocommerce-markdown
Command: npx skills add https://github.com/mwathiben/PropManager --skill woocommerce-markdown-mwathiben

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams write and lint WooCommerce Markdown to ensure consistency, readability, and compliance with the project's markdown standards.

Core Features & Use Cases

  • Enforces ATX headings style
  • Ensures 4-space indentation for lists
  • Requires code blocks to specify a language and use proper formatting
  • Guides creation and modification of documentation across WooCommerce projects

Quick Start

Run markdownlint from the repository root to lint all Markdown files against the configured rules

Frequently Asked Questions about woocommerce-markdown

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

FAQPage Schema
How do I lint WooCommerce Markdown files for consistent documentation formatting?

WooCommerce Markdown linting enforces consistent formatting by checking files against configured markdownlint rules for ATX headings, 4-space list indentation, and properly specified code block languages. This ensures documentation remains readable and compliant with project standards.

What Markdown style rules does the WooCommerce documentation project enforce?

WooCommerce Markdown style rules enforce ATX-style headings, 4-space indentation for lists, and code blocks that specify a language with proper formatting. These rules ensure repository documentation, README files, and CLAUDE.md guidelines maintain consistent styling and readability.

Do I need markdownlint installed to standardize formatting across WooCommerce projects?

Yes, markdownlint is required to standardize formatting across WooCommerce projects. Running it from the repository root applies the configured linting rules to all Markdown files, validating headings, lists, code blocks, and encoding to satisfy the project's markdownlint configuration requirements.

Why does my WooCommerce Markdown linting fail on code blocks and lists?

Markdown linting fails on code blocks when they lack a specified language or proper formatting, and fails on lists without 4-space indentation. Running markdownlint from the repository root identifies these violations so you can adjust documentation to meet the configured WooCommerce styling rules.

What's the best way to maintain consistent Markdown guidelines in WooCommerce repository documentation?

The best way to maintain consistent Markdown guidelines is to run markdownlint from the repository root against all Markdown files. This applies the project's configured rules for headings, lists, code blocks, and encoding to ensure documentation adheres to WooCommerce markdown standards.