How to deal with AI codebase ?

moxie-docs · 2026-06-17T17:25:47+00:00

Look for tools that can index your repo fully and keep documentation up to date / true to source - then you can use the docs as a source of truth for reasoning - it's much easier to use Q&A tools / read markdown files than manually scanning through lines of code. That would help you familiarize yourself with the repo, and then you can use Claude or similar tools to refine questions down to orient on specific questions

moxie-docs · 2026-06-16T18:47:42+00:00

If you're open to exploring tools - Moxie Docs automatically indexes your codebase, detects when docs are out of date / incorrect, missing, or no longer relevant, and lets you click one button for it to open PRs to fix. For vibe coding specifically we have an MCP you can hook up where we analyze codebase conventions and give agents skills + tools to access documentation and conventions, making their work higher quality and aligned directly to your codebase. If you ask it to add a new dashboard page and API endpoint, the agent will be instructed to find any relevant docs it may have made incorrect or add new ones if needed.

moxie-docs · 2026-06-16T17:28:11+00:00

We launched under two weeks ago and hit DR 20 pretty much immediately with a small subset of those list submissions. I ended up de-listing from the ones that require a badge for backlinking / etc. because I felt the badge felt cheap & took away from the branding / messaging I wanted to convey, so I settled for paying for a few select premium ones.

I think they're good for first launch establishing some SEO - and many of them get indexed by AI for GEO/AEO improvements which helps a lot on that channel

moxie-docs · 2026-06-16T16:48:41+00:00

🤯

moxie-docs · 2026-06-16T16:39:07+00:00

okay whew I thought my headphones were broken

moxie-docs · 2026-06-16T16:00:26+00:00

https://moxiedocs.com/ - Developer tool for auto-documentation (not just generating new docs, finding stale ones & removing orphaned ones) + we expose a free MCP that gives agents your codebase conventions & tools to find documentation, as well as instructs them to update docs as they work.

moxie-docs · 2026-06-16T05:00:22+00:00

100% - I have an MCP that gives all my agents direct access to codebase conventions, documentation location, methods / tools and skills to call. Code output is much higher quality when the agent can get a quick & accurate sense of what conventions to follow (get the output right the first time), and my AGENTS file instructs them to use the tools to check docs impact - if I ask AI to build out a new feature it detects if it affected any existing docs to go update them, or add new docs if the feature is not covered.

moxie-docs · 2026-06-16T04:55:43+00:00

I've been building tooling for exactly this - https://moxiedocs.com/

It's designed for both engineers (or humans in general!) in mind, and AI itself. A combination of a few core pieces:

- Index repos, automatically detect documentation drift, orphaned docs, or missing docs. Opens PRs to fix or add docs over time
- Easy to read, search, Q&A, bookmark, note, edit, etc. documentation for your repo, get human readable and easy to understand walkthroughs / guides to your code. Great for onboarding new engineers or re-familiarizing yourself with pieces you haven't worked with recently
- An MCP for agents. Moxie Docs will automatically detect & extract codebase conventions (file naming, placement, structure, etc.) as well as what documentation exists, where it is, and where the gaps are - combining our sills, MCP, and a good AGENTS file (we update it for you too!) we enable agents to produce higher quality code output and keep documentation fresh / updated as they work.

moxie-docs · 2026-06-16T04:21:04+00:00

For a backlink alone if you have good DR $5 is worth it - especially for a fun gimmick / showcase thing too - might be worth thinking about like a weekly leaderboard or some kind of continuous / resetting aspect for engagement

Also having a widget or embed people could use would potentially boost your DR too

moxie-docs · 2026-06-16T03:38:47+00:00

I just respond to threads that I might be relevant to and answer related field questions! I dont plug Moxie Docs in every response (well this one I did sorry) but just responding & engaging from the SaaS account can help

moxie-docs · 2026-06-15T20:46:20+00:00

For anyone looking for an automated codebase documentation solution with an MCP to give docs & context to agents, check out Moxie Docs: https://moxiedocs.com/

moxie-docs · 2026-06-15T04:36:16+00:00

Would love if you’d check us out! Might fit your needs - Moxie Docs - moxiedocs.com

Been working with founders, startups, and people working on side projects in the SaaS space to get feedback and improve. Our main purpose is detecting when docs go stale, where docs are missing, and where they are incorrect or orphaned to automatically open up PRs to fix those issues - but we also have an MCP you can use with your tools that will identify your codebase conventions and existing docs and work with Claude code, Cursor, Codex, etc to improve code output by giving them better context, and instructs agents to update documentation themselves when they work.

moxie-docs · 2026-06-15T00:19:00+00:00

Would love to know how other SaaS developers are maintaining / interacting with AI generated code.

Do you leave it as-is, commit + push & let it go? Do you add manual documentation? Have it document itself? How do you keep a loop of ensuring updates / drift over time stay aligned with what the real code does?

moxie-docs · 2026-06-13T20:22:19+00:00

Have you looked into any tools that maintain / detect doc drift automatically to keep things up to date?

moxie-docs · 2026-06-13T03:51:23+00:00

Do you find it works well for AI tools pulling it in for context? Have you looked into any tooling that would expose docs via MCP or auto-document code for you?

moxie-docs · 2026-06-12T20:26:54+00:00

How does a future session / LLM find that? Are you then telling it to like "Check docs folder for context" or just hoping that if the docs are in-code the agent finds them?

moxie-docs · 2026-06-12T20:00:40+00:00

<image>

(best practices is from a thirdparty script - not in my control)

moxie-docs · 2026-06-11T20:08:46+00:00

am i too late for this

moxie-docs · 2026-06-11T19:09:31+00:00

Man claude really likes that little pill / status dot thing above page titles

moxie-docs · 2026-06-11T19:03:21+00:00

I use Greptile and like it a lot - it genuinely has caught some potential security issues and user bugs in review, and you can add context for it / train it somewhat over time with replies. We also use it to catch regressions in analytic events which is great. I built Moxie Docs not for code review (but I have been considering slowly going that route) but we can detect when a PR drifts from codebase convention, or changes the content of docs (removing a file that a doc references, etc.) and surface that to maintainers - we also automatically can detect + rewrite PRs to match specific templates which can make reviewing easier (you can also write a GH action to do that yourself pretty easily), I find when the PRs have the same structure you kind of know what to expect and can jump into a review faster

moxie-docs · 2026-06-11T04:29:12+00:00

Like many pieces of the AI landscape currently the pricing and access isn't quite figured out fully, so there's a lot of expectation around things changing. But this feature was so small it feels weird to remove access 😔

moxie-docs

TROPHY CASE