fix-markdown-fences

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 pattern below outside a block. Record indent level and enter "inside block" state.
2. Detect malformed closing fence: While inside a block, line matches the malformed closing pattern below. Insert a proper closing fence before this line.
3. Detect valid closing fence: Line matches the valid closing pattern below. Exit "inside block" state.

Regex patterns:

^\s*```[\w+-]+
^\s*```[\w+-]+\s*$
^\s*```\s*$

• [ ] No closing fences contain language identifiers
• [ ] Markdown renders correctly in preview
• [ ] git diff shows only fence-closing changes, no content modifications

Anti-Patterns

Avoid	Why	Instead
Manually searching for bad fences	Error-prone in large files	Use the algorithm or grep pattern
Copying opening fence line to close a block	Creates the exact bug this skill fixes	Always use plain ``` for closing
Fixing fences without tracking block state	Misidentifies nested vs sequential blocks	Use the stateful line-by-line algorithm

Prevention

When generating markdown with code blocks:

1. Always use plain ``` for closing fences
2. Never copy the opening fence line to close
3. Track block state when programmatically generating markdown

<details> <summary><strong>Implementation: TypeScript (Recommended)</strong></summary>

const OPENING_PATTERN = /^(\s*)```(\w+)/;
const CLOSING_PATTERN = /^(\s*)```\s*$/;

function repairMarkdownFences(content: string): string {
  const lines = content.split(/\r?\n/);
  const result: string[] = [];
  let inCodeBlock = false;
  let codeBlockIndent = "";

  for (const line of lines) {
    const openingMatch = line.match(OPENING_PATTERN);
    const closingMatch = line.match(CLOSING_PATTERN);

    if (openingMatch) {
      if (inCodeBlock) {
        result.push(codeBlockIndent + "```");
      }
      result.push(line);
      codeBlockIndent = openingMatch[1];
      inCodeBlock = true;
    } else if (closingMatch) {
      result.push(line);
      inCodeBlock = false;
      codeBlockIndent = "";
    } else {
      result.push(line);
    }
  }

  if (inCodeBlock) {
    result.push(codeBlockIndent + "```");
  }

  return result.join("\n");
}

</details>

<details> <summary><strong>Implementation: Bash (Quick Check)</strong></summary>

# Find files with potential issues
grep -rEn --include="*.md" -- '```\w+' . | grep -vE "^[^:]*:[0-9]*:[[:space:]]*```\w+[[:space:]]*$"

</details>

<details> <summary><strong>Edge Cases Handled</strong></summary>

1. Nested indentation: Preserves indent level from opening fence
2. Multiple consecutive blocks: Each block tracked independently
3. File ending inside block: Automatically closes unclosed blocks
4. Mixed line endings: Accepts both \n and \r\n as input (normalizes output to \n)

</details>