WikiFix for Confluence
Find and fix issues in your knowledge base
81 followers
Find and fix issues in your knowledge base
81 followers
WikiFix monitors your KB for issues like contradicting pages, duplicates and orphans, and fixes them in one click once you approve, so your team can trust what it reads or hears from AI.
Interactive
Free Options
Launch Team / Built With
Hey Product Hunt! Rezgar from the video here.👋
After heaps of experimenting and benchmarking, I'm excited to bring you WikiFix! Big thanks to @fmerian and @oobydrnk for getting this launch off the ground!
If you've ever handled an incident with a broken runbook, failed audit due to stale compliance docs, or onboarded someone with outdated guides, you may appreciate a way to keep those docs clean and consistent without frequent manual reviews.
WikiFix monitors your spaces for issues - in v1 it's contradicting claims, duplicate and orphan docs. It asks you which answer is right, and writes a fix. You approve every edit and undo it in one click.
That's v1, which only looks inside Confluence. Next could be checking docs against code, configs, or Notion - we'll work out what matters most together.
Before launch I scanned a few publilc spaces (https://wikifix.ai/examples/). Even carefully maintained public docs from brilliant teams are not immune - NASA (57 conflictcts across 732 docs), GitLab (332 in 4,576), Sourcegraph (86 in 901), Kafka (168 in 1629)... E.g. Europa Clipper's electronics vault is made of: aluminum-zinc alloy or titanium/aluminum? 🛰️
Got a space you'd bet is fully consistent? Make it your first scan. If WikiFix finds nothing useful there, tell me, and get your credits back twice over.
I'm around all day. Ask me anything!
FAQ:
It's AI, so some findings are wrong: about 1 in 5 when we hand-checked them, depending on the wiki. WikiFix has a feedback button, and that's what we tune on.
Rovo (or any AI assistant for that matter) can help with targeted pages and problems, but not in spotting issues across the board. They start from your question and fetch the few pages likely to answer it. While finding contradictions starts from no question and puts every claim next to every other claim on the same topic or relevant code.
WikiFix starts out as a Confluence app but will go standalone in v2. Tell us if you want your KB platform supported.
How does WikiFix decide which page is actually the correct one?
WikiFix doesn't judge. It presents you contradictions as multiple-choice questions like "Who may sign off an exception for a High or Medium risk?". With options and quotes.
If you know the answer, you choose it and WikiFix updates the relevant pages. If not - you can send it to Page/Space owner to decide.
Regular users browsing Confluence will also see a badge saying "X issues found" and can apply an answer if they know it.
confluence docs rot so fast, this is usefull 🙌 does it catch stale screenshots too?
@petrkovacik Today it can't, but it's an interesting case. Is it about old UI screenshots embedded in some kind of guides/runbooks? Were you thinking of spotting old screenshots not matching new ones? Or not matching actual UIs?
We know that it is common that UIs change - both own and 3rd party, functionality changes shape/place, causing instructions to go state. It is on our radar, but certainly not a low-hanging fruit.
Is it a common theme in your docs? Can you tell us more?
the "broken runbook during an incident" example is the one that got me, that's exactly the moment stale docs cost the most and it's the worst possible time to realize the page you're trusting is 8 months out of date. one thing I'm curious about on the contradiction detection: when two pages disagree, is it always because one is just wrong, or does it ever show you a case where both were correct at different points in time, like a page describing a feature before and after it changed behavior? "pick which answer is right" assumes a single ground truth, but some of our worst doc rot at Dial was actually two true statements from different months that nobody dated clearly
@galdayan Very interesting question, Gal, thanks. Do I read it correctly that you actually want such docs to coexist, you just want it to be clear which version/month a particular doc describes?
There are 2 components to the problem as I see it: Detection and Mitigation.
Detection is usually the trickier part. WikiFix can help with it today - it'll find statements that can't be true at the same time, notify you, surface it in the report, and show issue detected on relevant pages.
Mitigation at this point, is mostly convenience - AI drafting a fix vs somebody spending 5 mins to amend the doc. Instead of making it say the same thing, you can just annotate it appropriately.
How are you usually dealing with it? Amend the content with a clear month/version? Does the editor get it from memory or some reference data/metadata?
In your example where a page is describing Before and After behavior, WikiFix would not flag it. We're deliberately not looking for contradictions within one page, because before/after or good/bad example are much more common than actual contradictions within one doc, resulting in a swarm of false positives nobody wants to see.
@rezgar honestly, no system - it's mostly tribal knowledge, somebody pings in slack asking who wrote the page last and whether it's still true. no version/month tagging at all, which is exactly how we ended up with two true-at-different-times pages nobody could tell apart. the detection/mitigation split makes sense though, and good to know before/after on one page is intentionally out of scope. does the contradiction check stay scoped to pages written close together in time, or would it just as easily flag a page from a year ago against one from last week if they disagree
@galdayan Today we don't discriminate by date. If docs contradict, we'll flag them, regardless of their date. As long as they are in spaces you've chosen as scope.
The "only show docs created/edited within X months from each other" filter is technically trivial, can you tell me more about the use case?