fix-markdown-fenceslisted

# Fix Markdown Code Fence Closings Scan and repair malformed closing fences in markdown files. Closing fences must never contain language identifiers. ## Triggers | Trigger Phrase | Operation | |----------------|-----------| | `fix markdown fences` | Scan and repair malformed fence closings | | `repair code block closings` | Fix closing fences with language identifiers | | `markdown rendering broken` | Diagnose and fix fence issues | | `code blocks bleeding into content` | Fix unclosed or malformed fences | | `validate markdown code blocks` | Check all fences for correctness | ## Quick Reference | Symptom | Cause | Fix | |---------|-------|-----| | Code block bleeds into text | Closing fence has language identifier | Remove identifier from closing fence | | Nested blocks render wrong | Missing closing fence before new opening | Insert closing fence | | Content cut off at end of file | Unclosed code block | Append closing fence | ## When to Use **Use this skill when:** - Markdown code blocks render incorrectly or bleed into surrounding content - Closing fences have language identifiers (e.g., ` ```python ` instead of ` ``` `) - Validating markdown documentation before committing **Use manual editing instead when:** - The issue is indentation or content inside the code block (not the fences) - You need to change the language identifier on opening fences ## Process Track fence state while scanning line by line: 1. **Detect opening fence**: Line matches the opening p