lint-markdown
Skill0 starsChanged 9 months agoMITView on GitHub
Check and fix formatting and other issues in markdown files using markdownlint-cli2
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Azure/azure-sdk-for-rustedited, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Azure/azure-sdk-for-rust★ 88712% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- check-spellingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Check markdown files for common mistakes.
- Very specific: line 12
Run npm install from the repository root to install markdownlint-cli2 from devDependencies in the root package.json.
- Very specific: line 26
Run npx markdownlint-cli2 to lint Markdown files according to the configuration.
- Very specific: line 30
Run with the --fix flag to automatically fix supported issues:
- Distinctive: line 38
Run the same lint command again to verify all issues are fixed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Markdown linting
Check markdown files for common mistakes.
Installation and usage
Run npm install from the repository root to install markdownlint-cli2 from devDependencies in the root package.json. Then run npx markdownlint-cli2 <command> to use the locally installed version.
Configuration
The markdownlint-cli2 configuration is in .markdownlint-cli2.yaml at the repository root.
The configuration has the following structure:
globs: file patterns to lint (currently**/*.md), so no command-line arguments are needed.ignores: paths excluded from linting.config: markdownlint rule overrides (e.g.,first-line-h1,line-length,ol-prefix).
Check Markdown
Run npx markdownlint-cli2 to lint Markdown files according to the configuration.
Fix issues
Run with the --fix flag to automatically fix supported issues:
npx markdownlint-cli2 --fixTesting
Run the same lint command again to verify all issues are fixed. There should be no errors reported.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.