# Lint and Fix Markdown Documents

Markdown files often drift from project style rules and become harder to maintain. This skill guides Claude, Codex, and Claude Code through markdownlint-cli2 checks, fixes, and clear reporting.

## Install

```bash
npx skillstore add 46ki75/markdown
```

## Metadata

- Status: approved
- Slug: 46ki75-markdown
- Skillstore revision: r1
- Version status: missing
- Tree hash: e6deb4584133ec0983bcebf7166da9514c4982d8076bc7668792e87985846312
- Author: 46ki75
- GitHub username: 46ki75
- License: MIT
- Repository: https://github.com/46ki75/skills/tree/main/public/markdown
- Ref: 14dc8f201a64f8d30fd131d7f036cd5e788be523
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/46ki75-markdown
- Manifest: https://skillstore.pages.dev/api/skills/46ki75-markdown/manifest

## Capabilities

- Guides markdownlint-cli2 auto-fix runs for one or more Markdown files.
- Checks remaining Markdown lint errors after automated formatting.
- Explains common markdownlint rules such as heading levels, long lines, and code fences.
- Applies manual cleanup guidance for issues auto-fix cannot resolve.
- Helps create or adjust markdownlint configuration for project needs.
- Summarizes initial errors, automated fixes, manual edits, and final validation results.

## Use Cases

- Clean Pull Request Documentation: Lint README updates, fix common style issues, and report what changed before review.
- Standardize Documentation Sets: Apply consistent markdownlint rules across guides, tutorials, and reference pages.
- Prepare User-Facing Guides: Find heading, spacing, and formatting issues before publishing Markdown content.

## Prompt Templates

### Check One File

```
Check this Markdown file for lint issues. Explain the main problems and suggest safe fixes before changing it.
```

### Auto-Fix and Report

```
Run the Markdown auto-fix workflow on this file, then report the initial errors, remaining issues, and final result.
```

### Fix Manual Lint Issues

```
Review the remaining markdownlint errors. Fix heading hierarchy, emphasis-as-heading, and line wrapping issues while preserving meaning.
```

### Tune Project Rules

```
Review this project documentation style. Propose a markdownlint configuration and apply it to the selected files with a change summary.
```

## Limitations

- Requires markdownlint-cli2 to be installed in the execution environment.
- Can modify files when auto-fix is used, so changes should be reviewed.
- Cannot infer every project writing convention without user guidance.
- Does not validate rendered output, links, or factual accuracy beyond lint rules.

## Best Practices

- Run lint checks before and after edits so the final state is clear.
- Review auto-fix changes when files contain generated content or complex examples.
- Use a project configuration when documentation intentionally differs from default rules.

## Anti Patterns

- Running broad auto-fix commands across a repository without confirming scope.
- Disabling lint rules globally when only one document needs an exception.
- Changing document hierarchy only to satisfy lint rules without checking meaning.

## Security Audit

- Audited at: 2026-07-04T17:36:51.608\+00:00
- Summary: The static analyzer matched Markdown fences and inline code as Ruby backtick execution. Review found documented markdownlint-cli2 usage and a public documentation URL, with no prompt injection, data exfiltration, or arbitrary command construction in SKILL.md.

## Stats

- Views: 276
- Downloads: 24
- Favorites: 0
- Popularity score: 0