slideops

Technical documentation and presentations often become obsolete the moment the code changes. SlideOps solves this by generating HTML slide decks and Markdown docs grounded in the actual repository, using a citation system to verify accuracy. It eliminates the guesswork of "is this still true" by linking every code snippet and claim to specific file hashes and line ranges.

What it does

• Grounded generation Creates self-contained HTML slide decks or Markdown docs based on real repository code, logs, and architecture.
• Automated verification Uses a citation mechanism to check if documentation matches the current state of the repo in milliseconds.
• Drift detection Identifies moved, changed, or missing code references and provides a diff-based repair brief for stale slides.
• Visual consistency Offers four professional theme presets (Ledger, Midnight, Graphite) with responsive layouts and navigation.
• CI/CD integration Provides scripts to fail builds or annotate pull requests when documentation stops matching the code.

How it works

1. Research The agent scans the repository, git history, and existing docs to propose concrete topics and an outline.
2. Build The agent populates a self-contained HTML template with cited code snippets and Mermaid diagrams.
3. Verify Headless Chrome renders each slide to ensure no text overlaps or layout breaks, while a Python script validates all citations.
4. Sync You run check.py to identify drift; the agent then repairs only the specific slides that no longer match the code.

Frameworks & tools

This skill requires a headless Chrome or Chromium binary (system install or Playwright). It uses Python 3 for the verification scripts and interacts with repositories via standard git commands.

Why this beats prompting it yourself

Generic prompts often hallucinate code structure or produce layouts that break when rendered. SlideOps enforces a strict citation-and-hash system that makes documentation provably accurate and provides automated visual QA that manual prompting cannot replicate.

Use cases

• Onboarding decks Create a "project in one picture" overview for new hires that stays current.
• Deep-dive architecture Document complex subsystems with diagrams and snippets that link to real source files.
• Release summaries Generate "what's new" decks for stakeholders by analyzing recent git commits and diffs.
• Doc-to-code syncing Ensure Markdown design docs in the repo never drift from the implementation.

Known limitations

Requires a local Chrome/Chromium installation for visual verification. Mermaid diagrams and brand color extraction require optional network access. Designed for repository-based technical decks.