write-run-markdown-lint
Run Markdown Lint
Lint one Markdown file with markdownlint-cli2 and the user's config, then report what is really wrong. This skill is read-only unless the user approves fixes.
Why the tool choice matters
Use markdownlint-cli2 only. Never fall back to markdownlint (markdownlint-cli v1, which Homebrew installs). The user's config is a cli2 options file with the rules nested under "config". v1 treats that key as an unknown rule, drops every setting, and lints with defaults. The result looks plausible and is wrong both ways: it reports MD013 at 80 columns, MD052 on Hugo {{< ref >}} shortcodes, MD010, and MD034, which the user turned off or relaxed. It also flags correct * lists under MD004 and lets - lists pass. On a clean published article, v1 reports 83 findings where cli2 reports 0.
Workflow
-
Get the file. Use the path the user gave. If they gave none, ask which file to lint. Lint the file where it is; do not copy it.
-
Run the bundled script.
bash <skill-dir>/scripts/lint.sh <file> [--config <path>]