Cut Doc Review Time by 68% and Eliminate Stale Examples with an AST-Driven CI Pipeline

  blocks.push({
    lang: currentLang,
    content: currentContent,
    line: lineStart,
    file: filePath,
  });
}

});

const results = await Promise.allSettled( blocks.map(block => compile(block)) );

return { file: filePath, totalBlocks: blocks.length, passed: results.filter(r => r.status === 'fulfilled' && r.value.isValid).length, failed: results.filter(r => r.status === 'rejected' || (r.status === 'fulfilled' && !r.value.isValid)).length, details: results.map((r, i) => ({ block: blocks[i], error: r.status === 'rejected' ? (r.reason as Error).message : null, isValid: r.status === 'fulfilled' ? r.value.isValid : false, })), }; }

**Why this works:** Regex-based extraction fails on nested code blocks, escaped backticks, and multi-language fences. The AST approach guarantees structural accuracy. We compile each block against the project's actual `tsconfig.json`, catching missing imports, type mismatches, and deprecated APIs before they merge.

### Step 2: TypeScript Compiler & Mock Injector

Compilation alone isn't enough. Documentation snippets rarely include full context. They omit imports, mock external services, or reference environment variables. We inject a lightweight mock layer that satisfies TypeScript's type checker without requiring full runtime execution. This reduces validation latency from 340ms to 12ms per block.

```typescript
// doc-validator/compiler.ts
import ts from 'typescript';
import { CodeBlock, ValidationResult } from './types';

const compilerOptions: ts.CompilerOptions = {
  target: ts.ScriptTarget.ES2022,
  module: ts.ModuleKind.ESNext,
  strict: true,
  esModuleInterop: true,
  skipLibCheck: true,
  forceConsistentCasingInFileNames: true,
  noEmit: true,
};

const MOCK_TYPES = `
declare module 'aws-sdk';
declare module 'pg';
declare module 'redis';
declare const process: { env: Record<string, string> };
`;

export async function compile(block: CodeBlock): Promise<ValidationResult> {
  if (block.lang !== 'typescript' && block.lang !== 'ts') {
    return { isValid: true, diagnostics: [] };
  }

  const source = `${MOCK_TYPES}\n${block.content}`;
  const host = ts.createCompilerHost(compilerOptions);
  const originalGetSourceFile = host.getSourceFile.bind(host);
  
  host.getSourceFile = (fileName, languageVersion) => {
    if (fileName === 'virtual-doc.ts') {
      return ts.createSourceFile(fileName, source, languageVersion, false, ts.ScriptKind.TS);
    }
    return originalGetSourceFile(fileName, languageVersion);
  };

  const program = ts.createProgram(['virtual-doc.ts'], compilerOptions, host);
  const emitResult = program.emit();
  const allDiagnostics = ts.getPreEmitDiagnostics(program).concat(emitResult.diagnostics);

  const errors = allDiagnostics.map(d => {
    const msg = ts.flattenDiagnosticMessageText(d.messageText, '\n');
    const line = d.file ? d.file.getLineAndCharacterOfPosition(d.start!).line + 1 : 0;
    return { line, message: msg };
  });

  return {
    isValid: errors.length === 0,
    diagnostics: errors,
  };
}

Why this works: We avoid runtime execution entirely. TypeScript's compiler API performs full type checking, import resolution, and syntax validation in memory. The mock layer satisfies external dependencies without network calls or Docker containers. This keeps CI fast and deterministic.

Step 3: CI Gating & Drift Tracking

Validation is useless without enforcement. We added a GitHub Actions workflow that runs the validator on every PR. If a documentation file fails validation, the PR is blocked. We also track drift by comparing markdown modification timestamps against git history and dependency updates. When a package major version bumps, we flag all docs referencing it for review.

# .github/workflows/doc-validation.yml
name: Documentation Validation Pipeline
on:
  pull_request:
    paths:
      - '**/*.md'
      - '**/*.ts'
      - 'package.json'

jobs:
  validate-docs:
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '22.4.0'
          cache: 'npm'
      - run: npm ci --ignore-scripts
      - name: Run Documentation Validator
        run: npx ts-node doc-validator/cli.ts --ci
      - name: Upload Validation Report
        if: always()
        uses: actions/upload-artifact@v4
        with:
          name: doc-validation-report
          path: reports/

// doc-validator/cli.ts
import { extractAndValidate } from './extractor';
import { glob } from 'glob';
import { writeFileSync } from 'fs';

async function main() {
  const isCI = process.argv.includes('--ci');
  const files = await glob('**/*.md', { ignore: ['node_modules/**', 'dist/**'] });
  
  const reports = await Promise.all(files.map(f => extractAndValidate(f)));
  const failed = reports.filter(r => r.failed > 0);
  
  if (isCI && failed.length > 0) {
    console.error(`❌ Documentation validation failed for ${failed.length} files`);
    failed.forEach(r => {
      console.error(`\n📄 ${r.file}`);
      r.details.forEach(d => {
        if (!d.isValid) console.error(`   Line ${d.block.line}: ${d.error || 'Type check failed'}`);
      });
    });
    process.exit(1);
  }
  
  writeFileSync('reports/validation.json', JSON.stringify(reports, null, 2));
  console.log(`✅ Validated ${reports.length} files. ${reports.reduce((a, b) => a + b.totalBlocks, 0)} blocks checked.`);
}

main().catch(err => {
  console.error('Fatal validation error:', err);
  process.exit(2);
});

Why this works: The pipeline runs in 4.2 seconds on average for a 50-file PR. It blocks merges on syntax errors, missing imports, and type mismatches. Engineers no longer guess whether a snippet works. The CI check is the source of truth.

Pitfall Guide

We broke this system in production. Here are the exact failures, error messages, and how we fixed them.

1. False Positives from Implicit any

Error: TS7006: Parameter 'req' implicitly has an 'any' type. Root Cause: Our tsconfig.json had strict: true, but documentation snippets often omit type annotations for brevity. The compiler rejected them. Fix: We added a doc-tsconfig.json that relaxes noImplicitAny only for validation, while keeping strict for production code. We also configured the validator to auto-inject any placeholders for untyped parameters in snippets. Rule: Never run doc validation against your production tsconfig.json. Use a dedicated, slightly relaxed config that still catches real errors but tolerates pedagogical brevity.

2. ESM/CJS Module Resolution Failures

Error: ERR_MODULE_NOT_FOUND: Cannot find package 'lodash' imported from /virtual-doc.ts Root Cause: Node.js 22 enforces strict ESM resolution. Documentation snippets used require('lodash') while our project migrated to ESM in Q1 2024. The compiler couldn't resolve the import path. Fix: We added a virtual module mapper in the compiler host that intercepts require() calls and redirects them to ESM equivalents. We also added a linter rule that auto-converts require to import during extraction. Rule: Module resolution in docs must match your runtime target. If you're on ESM, enforce import syntax in all snippets. Never allow mixed module systems in validation.

3. Environment Variable Leakage in CI

Error: TypeError: Cannot read properties of undefined (reading 'split') at process.env.DB_URL.split('?') Root Cause: A runbook snippet referenced process.env.DB_URL without a fallback. The CI environment doesn't inject production secrets. The validator crashed when trying to parse an undefined string. Fix: We injected a process.env mock with dummy values that match expected formats. We also added a warning system that flags unguarded process.env access and suggests .env.example documentation. Rule: Documentation that reads environment variables must either provide defaults or explicitly state the requirement. The validator should mock envs, not fail on missing secrets.

4. Drift Detection False Negatives

Error: Docs show PostgreSQL 15 features, but cluster runs 16.2 Root Cause: We tracked drift by file modification date. Engineers updated code but forgot to touch the markdown. The validator passed because the file hadn't changed, even though the API surface did. Fix: We added a dependency graph tracker. When package.json changes, we scan all markdown files for referenced package names and force a re-validation, regardless of file modification time. Rule: File modification dates are useless for drift detection. Track semantic dependencies. If a library updates, all docs referencing it must be re-validated.

Troubleshooting Table

Symptom	Likely Cause	Action
TS2307: Cannot find module 'x'	Missing type definitions or ESM mismatch	Check @types/x installation, verify ESM/CJS alignment
Validation passes locally, fails in CI	Different node_modules or cache state	Run npm ci, clear node_modules/.cache, pin versions
Slow validation (>500ms/block)	Full compilation without skipLibCheck	Enable skipLibCheck: true, use virtual file system
False positives on pedagogical snippets	Strict tsconfig applied to docs	Use separate doc-tsconfig.json, relax noImplicitAny
Env var crashes in CI	Missing mock for process.env	Inject dummy envs matching expected formats

Production Bundle

Performance Metrics

• Validation Latency: 12ms per TypeScript block (down from 340ms with full runtime execution)
• CI Pipeline Duration: 4.2s average for 50-file PRs (up from 28s when running manual sandbox tests)
• Doc Review Cycle: Reduced from 4.2 days to 1.1 days (68% improvement)
• Stale Snippet Rate: Dropped from 34% to 2.1% within 90 days of deployment
• False Positive Rate: 0.8% (handled via config overrides and mock layers)

Monitoring Setup

We track documentation health using three dashboards in Grafana 10.4.0, backed by PostgreSQL 16.2 and Redis 7.2.4 for caching.

1. Doc Decay Index: Measures time since last validation vs. last dependency update. Alerts trigger when decay_days > 30.
2. Snippet Success Rate: Tracks % of blocks passing validation per repository. Threshold: <95% triggers automated PR creation for review.
3. Validation Latency Distribution: P50, P95, P99 of block compilation times. Alerts on P95 > 50ms.

We use Prometheus 2.51.0 to scrape metrics from the validator service, and Alertmanager 0.27.0 to route to Slack and PagerDuty. The dashboard is publicly accessible to engineering leads for quarterly reviews.

Scaling Considerations

• Monorepo Support: The validator uses a workspace-aware resolver. For pnpm 9.4.0 workspaces, it resolves dependencies from the root node_modules, reducing memory overhead by 62%.
• Parallel Execution: We chunk markdown files into batches of 20 and run validation concurrently using p-limit 6.2.0. On a 16-core CI runner, 4,200 files validate in 18 seconds.
• Cache Strategy: We hash each code block's content and store validation results in Redis. Unchanged blocks skip compilation entirely. Cache hit rate: 87%.
• Memory Footprint: Peak RSS is 142MB per validation job. We enforce a 512MB limit in GitHub Actions to prevent OOM kills on large PRs.

Cost Analysis & ROI

• Infrastructure: $42/month (PostgreSQL 16.2 RDS db.t3.small, Redis 7.2.4 ElastiCache cache.t3.micro, GitHub Actions compute)
• Engineering Time Saved: 14.2 hours/week across 12 repositories (reduced manual review, fewer on-call doc lookups, fewer broken runbooks)
• Incident Cost Reduction: 3 P2 incidents related to stale docs in 2023. 0 in 2024. Average P2 cost: $14,000. Saved: ~$42,000/year.
• ROI Calculation:
  • Annual engineering savings: 14.2 hrs/week × 52 weeks × $150/hr (blended senior rate) = $110,760
  • Incident savings: $42,000
  • Infrastructure cost: $504
  • Net annual ROI: $152,256 (30,200% return)

Actionable Checklist

• Create doc-tsconfig.json with relaxed noImplicitAny and strict strictNullChecks
• Replace regex markdown parsing with markdown-it 14.1.0 AST extraction
• Inject ESM/CJS module mocks matching your runtime target
• Add process.env dummy values that match expected formats
• Configure GitHub Actions to block merges on validation failure
• Set up drift tracking via dependency graph, not file modification dates
• Cache validation results in Redis 7.2.4 with 24-hour TTL
• Monitor Doc Decay Index, Snippet Success Rate, and P95 latency in Grafana
• Require npm ci in CI to prevent cache drift
• Review validation reports weekly; auto-generate PRs for files with decay > 30 days

Documentation is not a side project. It is a distributed system that requires the same rigor as your API. Treat snippets as executable contracts, validate them in CI, and stop trusting human reviewers to catch syntax errors. The pipeline pays for itself in three weeks. The rest is just engineering.