slideops

SlideOps: slides from a repo, that tell you when they go stale

Catalog copy, frozen at v1.0.0. The canonical source is

glukicov/slideops, which also carries the deck

template, the two citation scripts, the reference docs, and the companion

slides-to-pdf skill. Install from there; this page summarizes the workflow.

Overview

SlideOps has two jobs, and the second one is the point. Build: turn a repository into a single self-contained HTML slide deck whose every claim came from the code, not from a model's impression of the code. Keep in sync: make that deck able to prove, months later, whether it still matches the repository.

The mechanism joining them is a citation. Every quoted snippet records the file, the line range, and a hash of those source lines at build time, and the deck records the commit it was built from. "Are these slides still accurate?" becomes a command instead of a re-read: a standard-library Python script diffs each citation against the current code and reports CURRENT, MOVED, CHANGED, or MISSING. No model, no network, no tokens, milliseconds to run.

When to Use This Skill

• Use when the user asks for slides, a slide deck, or a presentation about a code

repository, one of its subsystems, a feature, or its recent changes: "make slides", "overview deck", "team update slides",