markdown-standards

Enforce markdown linting standards across StakTrakr documentation files.

8|3|Updated Feb 6, 2026

Search Tags:#linting #documentation #markdown #standards #copilot #codacy

Ready to run

npx skills add https://github.com/lbruton/StakTrakr --skill markdown-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: markdown-standards
Source: https://github.com/lbruton/StakTrakr/tree/main/.claude/skills/markdown-standards
Command: npx skills add https://github.com/lbruton/StakTrakr --skill markdown-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures all markdown documentation within the StakTrakr repository adheres to strict linting rules, preventing common errors and maintaining a professional, consistent standard across all .md files.

Core Features & Use Cases

Automated Linting: Applies a comprehensive set of rules to identify and flag markdown formatting issues.
Codacy & Copilot Compliance: Helps avoid flags from automated code quality tools and AI assistants by enforcing best practices.
Use Case: When contributing to the StakTrakr documentation, this skill will automatically check your markdown for issues like missing blank lines around lists or code blocks, trailing spaces, or incorrect header usage, ensuring your changes meet the project's standards before submission.

Quick Start

Use the markdown-standards skill to check the formatting of the attached file 'README.md'.

Frequently Asked Questions about markdown-standards

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

FAQPage Schema

How do I enforce markdown linting standards across project documentation files?▼

To enforce markdown linting standards, you can apply automated rules that identify formatting issues like incorrect spacing around lists, improper header usage, and trailing whitespace, ensuring all `.md` files maintain a professional, consistent standard before submission.

What are common markdown formatting violations I should check before submitting documentation?▼

Common markdown formatting violations include missing blank lines around code blocks and lists, incorrect header usage, and trailing whitespace. Checking for these issues helps maintain documentation quality and prevents flags from automated code review tools.

How can I check markdown files for compliance with Codacy and Copilot quality tools?▼

You can check markdown files for Codacy and Copilot compliance by applying comprehensive linting rules that enforce best practices, preventing common formatting errors that would trigger flags from these automated code quality and AI assistant tools.

Does markdown linting require specific dependencies to check documentation formatting?▼

Markdown linting does not require specific external dependencies to check documentation formatting. The skill operates independently to identify and flag formatting issues within markdown files, applying project-wide quality guidelines without additional package installations.

How do I fix trailing whitespace and incorrect spacing in markdown documentation?▼

To fix trailing whitespace and incorrect spacing in markdown documentation, apply automated linting rules that detect and flag these specific violations. This ensures your `.md` files meet strict formatting standards and maintain consistent documentation quality.