DEV Community

Ned C
Ned C

Posted on • Originally published at nedcodes.dev

cursor-doctor v1.10: coverage gaps and README badges

what's new

I just shipped two features for cursor-doctor. One tells you what your rules are missing. The other gives you a badge to show off your health grade.

coverage gap detection (v1.10.25)

You have rules. But do they cover what matters?

cursor-doctor now scans your package.json or requirements.txt to detect your stack, then checks if your rules cover the categories that matter for that stack. Testing, error handling, accessibility, API patterns, security, performance.

Here's what it looks like:

npx cursor-doctor scan
Enter fullscreen mode Exit fullscreen mode
  ▒▒ Cursor Health: A ▒▒

  █████████████████████████████░  98%

  ✓ Rules exist
  ✓ Rule syntax
  ✓ Token budget
  ✓ Coverage
  ✓ File sizes

  7 passed  

  ▓ Coverage Report

  Detected:  react, nextjs
  Covered:   styling
  Missing:   testing, error-handling, state-management, 
             accessibility, performance, api-data-fetching, 
             security

  Suggestions:
    • testing: Testing rules help maintain code quality 
      and catch bugs early
    • error-handling: Error handling rules ensure robust 
      error management
    • state-management: State management rules prevent 
      common pitfalls
    ... and 4 more
Enter fullscreen mode Exit fullscreen mode

If you're building a React app with no testing rules, it tells you. If you're running Next.js with no API or security rules, it flags that. If you have 12 styling rules but nothing about error handling, you'll see it.

The suggestions are specific to your stack. A Django project gets different recommendations than a React app. A Rust project won't get nagged about CSS.

README badge generator (v1.10.26)

Your Cursor rules have a health grade. Now you can show it.

npx cursor-doctor badge
Enter fullscreen mode Exit fullscreen mode

Output:

cursor-doctor v1.10.26 -- badge generator

Markdown:
  ![Cursor Rules: A (98%)](https://img.shields.io/badge/Cursor%20Rules-A%20(98%25)-brightgreen)

HTML:
  <img src="https://img.shields.io/badge/Cursor%20Rules-A%20(98%25)-brightgreen" alt="Cursor Rules: A (98%)">

Dynamic Badge (shields.io endpoint JSON):
  Save this JSON to your repo and reference it:
  npx cursor-doctor badge --json > cursor-rules-badge.json
  https://img.shields.io/endpoint?url=https://yourrepo/cursor-rules-badge.json
Enter fullscreen mode Exit fullscreen mode

Copy the markdown snippet and paste it in your README. The badge shows your grade (A through F) with color coding. Green for A, yellow for C, red for F.

Cursor Rules: A (98%)

The badge is static by default. It shows the grade at the time you ran the command. If you want a dynamic badge that updates automatically, use the --json flag to generate a shields.io endpoint file, commit it to your repo, and reference it in your README.

why this matters

Most Cursor rules are written once and never looked at again. You add a rule for React hooks. Then you add Express. Then you add auth logic. The rules grow organically, and gaps emerge.

Coverage gap detection surfaces those gaps. It's not about telling you to write more rules. It's about telling you which rules would actually help.

The badge is a forcing function. If you put it in your README, you'll see when your health grade drops. If you're sharing rules with your team or in open source, it's a signal that someone is paying attention.

try it

Both features are free and available now:

npx cursor-doctor scan    # see coverage gaps
npx cursor-doctor badge   # generate badge snippets
Enter fullscreen mode Exit fullscreen mode

If you find issues in your rules, the Pro version has 34 auto-fixers. $9 one-time at nedcodes.gumroad.com/l/cursor-doctor-pro. If it doesn't find real, fixable problems, email hello@nedcodes.dev for a refund.

Full docs: github.com/nedcodes-ok/cursor-doctor

Top comments (0)