Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: SlideOps – slides from a repo that flag when they drift from the code

github.com

Post reply on HN
Print view View original

1–8 of 8 posts

Show HN: SlideOps – slides from a repo that flag when they drift from the code

#1

Post by lukicov »

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

Show HN: SlideOps – slides from a repo that flag when they drift from the code
github.com

Re: Show HN: SlideOps – slides from a repo that flag when they drift from the code

#3

Post by 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?

Re: Show HN: SlideOps – slides from a repo that flag when they drift from the code

#4

Post by boxed »

brookst wrote: post #3

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…

I wrote a bunch of custom tooling for iommi, I have a write up of it here: https://kodare.net/2025/08/08/documentation-that-is-never-wr...

Re: Show HN: SlideOps – slides from a repo that flag when they drift from the code

#5

Post by lukicov »

boxed wrote: post #4
brookst wrote: post #3

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…

I wrote a bunch of custom tooling for iommi, I have a write up of it here: https://kodare.net/2025/08/08/documentation-that-is-never-wr...

The framing that the test suite is the documentation stuck with me: executing the examples removes the duplication rather than tracking it. Taking ideas from this, thank you!

Re: Show HN: SlideOps – slides from a repo that flag when they drift from the code

#6

Post by boxed »

lukicov wrote: post #5
boxed wrote: post #4

Earlier quoted context omitted.

I wrote a bunch of custom tooling for iommi, I have a write up of it here: https://kodare.net/2025/08/08/documentation-that-is-never-wr...

The framing that the test suite is the documentation stuck with me: executing the examples removes the duplication rather than tracking it. Taking ideas from this, thank you!

We did it the other way around first, but it was a huge hassle and very hacky. Since we flipped it we've been much more satisfied with the system.

It's somewhat inspired by literate programming, but a bit flipped.

Re: Show HN: SlideOps – slides from a repo that flag when they drift from the code

#7

Post by lukicov »

brookst wrote: post #3

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…

Great idea on generalising this beyond just slides - v1.1 is now out with Markdown support :)

This invisible citation comment (On the topic of generlaising to documents, for a moment I wish I named the skills "DocOps", but that's already a thing: https://www.writethedocs.org/guide/doc-ops/

Post reply on HN