I rewrote my Cursor linter into a full diagnostic tool (and added auto-fix)

cursor-lint started as a thing I built because my own .mdc rules kept silently breaking. Missing frontmatter, bad YAML, alwaysApply not set. Cursor doesn't tell you when a rule fails to load. It just... doesn't load it. No error, no warning, nothing. That tool ended up getting ~1,800 downloads, which was cool, but I kept running into problems it couldn't solve. Like, I had two rules that contradicted each other ("use semicolons" in one file, "avoid semicolons" in another) and the linter had no way to catch that. Or I'd have rules with 80% identical content because I'd copy-pasted and forgotten to clean up. The linter could tell me if individual rules were well-formed, but it couldn't tell me if my setup was healthy. So I rebuilt it. cursor-doctor npx cursor-doctor scan The free scan gives you a health grade (A through F) based on 8 checks: whether rules exist, legacy .cursorrules conflicts, 20+ lint checks, token budget, file type coverage, file sizes, alwaysApply usage, and whether yo