Fix markdown lint warnings by enforcing headings, blank lines around lists, and language-tagged code fences for clean documentation.
Scanned 2/12/2026
Install via CLI
openskills install peterbamuhigire/skills-web-dev---
name: markdown-lint-cleanup
description: Fix markdown lint warnings by enforcing headings, blank lines around lists, and language-tagged code fences for clean documentation.
---
# Markdown Lint Cleanup
## Overview
Use this skill to clean markdown files so they pass lint checks with zero warnings. It focuses on consistent headings, spacing, and fenced code block language tags.
## When to Use
- Markdown lint warnings appear (MD022, MD032, MD036, MD040, MD031)
- Documentation updates need a clean lint pass
- Large docs need formatting normalization without content changes
## Core Rules (Required)
1. **Headings must be proper headings**
- Replace bold-only headings with `##`, `###`, etc.
2. **Blank lines around lists**
- Add a blank line before and after lists
3. **Blank lines around fenced code blocks**
- Surround code fences with blank lines
4. **Language tags on fenced code blocks**
- Use `bash`, `php`, `sql`, or `text` as appropriate
## Common Fixes
### MD036: Emphasis used instead of a heading
**Replace**:
**Section Title**
**With**:
## Section Title
### MD032: Blanks around lists
Ensure blank lines before and after lists:
Text paragraph.
- Item one
- Item two
Next paragraph.
### MD022: Blanks around headings
Add a blank line before and after headings:
Paragraph text.
#### Heading
- List item
### MD040: Fenced code language
Add a language identifier:
```text
Example output line
```
### MD031: Blanks around fences
Ensure fences are separated from other text:
Paragraph text.
```bash
php scripts/verify_uom_system.php
```
## File Safety
- Do not change meaning or content structure
- Only adjust formatting to satisfy lint rules
- Preserve links and references exactly
## Recommended Workflow
1. Identify lint warnings and their line numbers
2. Apply targeted fixes (headings, spacing, code fence languages)
3. Re-check lint until clean
## Output Expectations
- No markdown lint warnings
- No content meaning changes
- Consistent formatting across documents
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.