Generate slide decks from code with staleness detection

SlideOps has two jobs. The first is build: it turns a code repository into a single self-contained HTML slide deck whose every claim comes from the code itself, not from a model's impression of the code. The second, and the point of the skill, is keep in sync: it makes that deck able to prove, months later, whether it still matches the repository it was built from.

The mechanism joining the two jobs is a citation. Every quoted snippet in the deck records the file, the line range, and a hash of those source lines taken at build time, and the deck itself records the commit it was built from. That turns "are these slides still accurate" from a manual re-read into a command: a standard-library Python script diffs each citation against the current state of the code and reports one of four verdicts per citation - CURRENT, MOVED, CHANGED, or MISSING.

Use it when you need a slide deck, architecture walkthrough, or onboarding presentation whose claims are traceable to real lines of code, and where you expect the codebase to keep changing after the deck ships. It is not a general-purpose presentation generator: its value is entirely in the citation and re-verification loop, so it fits worst for content that has nothing to do with a codebase (pure narrative or strategy decks) or for a one-off deck nobody expects to keep accurate.

Input is a code repository. Output is a single self-contained HTML slide deck plus, on later runs, a per-citation drift report (CURRENT / MOVED / CHANGED / MISSING) comparing the deck against the current repository state.

The re-verification step runs as a standard-library Python script - no external model call, no network request, and it completes in milliseconds. This is a deliberate design point of the skill: checking whether a deck is stale is meant to be cheap enough to run constantly, not an occasional re-read.

Teams that maintain a living reference deck - architecture overview, onboarding walkthrough, internal documentation - against a codebase that keeps moving, and who want a fast, automatic way to know when that deck has fallen out of date rather than discovering it by accident.