verifying-markdown-formatting
Verifying Markdown Formatting
Check a Markdown file for formatting issues and fix them.
What to Check
Structure
- Exactly one
# H1heading at the top of the file - Headings increment by one level (no jumping from
##to####) - Blank line before and after every heading
- Blank line before and after every code block, list, and blockquote
- File ends with a single trailing newline
Lists
- Consistent marker style within each list (
-not mixed with*or+) - Nested items indented with 2 or 4 spaces (consistent throughout)
- Blank line before the first item in a top-level list
More from spencerpauly/awesome-cursor-skills
saving-workspace-context
Automatically persist useful context — research, decisions, learnings, templates — to workspace files so knowledge survives across conversations.
38reviewing-code
Perform a thorough code review focused on correctness, maintainability, performance, and best practices.
37database-design
Design database schemas — tables, relationships, indexes, constraints, and ORM setup. Covers relational design, normalization, and common patterns.
36suggesting-cursor-rules
When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.
35systematic-debugging
Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.
33auditing-security
Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.
33