Show HN: SlideOps – slides from a repo that flag when they drift from the code
I kept generating slide decks about my codebases with an agent, and weeks later they would go stale. Updating them was quite costly (time & tokens), as the agent would have to re-scan the whole repo to re-generate the slides. So I made the slide deck carry its own provenance: SlideOps skill turns a repo into a slide deck, with all references to files carrying exact line range and a hash. Checking is done with standard-library Python: no model calls, no network, and very fast. For example, it distinguishes MOVED (the code shifted) from CHANGED (the content differs). Updating the slides costs tokens, but now the checking part has already given the agent just the relevant context on what exactly needs to be repaired. SlideOps ships as a Claude Code plugin and runs as a plain agent skill in Codex, Copilot CLI and OpenCode. Longer write-up: https://medium.com/@lukicov/your-documentation-is-a-build-ar... GitHub repo: https://github.com/glukicov/slideops
Discussion Highlights (1 comments)
brookst
I love this. Thanks for sharing. Would be great to generalize to documentation in general, not just slides. My LLM workflow is documentation-heavy, and that works great for getting projects off the ground and managing very large projects. But just like human-driven development, more documentation = more likelihood of being stale. Unlike humans, LLMs don’t resent time spent updating docs. So, if you’re taking feature requests, I would love to see this head towards full lifecycle documentation management. The tricky part is figuring out whether the docs or code drifted. Sometimes misalignment means the code was built wrong, sometimes it means the docs are stale and changes are intentional. A HITL model should maybe help?