slideops

# SlideOps: generate a deck from a repository, and keep it true This skill has two jobs, and the second one is the point. **Build**: turn a repository into a 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, cheaply enough that nobody has to remember to care. 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. That turns "is this deck still accurate?" from a question somebody has to answer by reading into a command that answers itself: ```bash python3 scripts/check.py docs/slides/ --repo . ``` Standard library only. No model, no network, no tokens, milliseconds to run. Two scripts ship with this skill and do all of it: [`scripts/cite.py`](scripts/cite.py) writes the citations while you build, and [`scripts/check.py`](scripts/check.py) reads them back afterwards. Writing the citations as you go (Step 3) is therefore not optional decoration: it is the entire reason the deck can be maintained instead of rewritten. See [`references/freshness.md`](references/freshness.md) for the mechanism and [`references/automation.md`](references/automation.md) for wiring it into pull requests, scheduled refreshes, and agent hooks. ## Which job is this? - The user wants a **new deck**: start at Step 0 below. -...