Moxie Docs llms.txt changelog

https://moxiedocs.com/llms.txt

− - [Automated code documentation](https://moxiedocs.com/code-documentation): Generate searchable codebase documentation from GitHub automatically. Architecture, conventions, cross-file flows, drift detection, MCP context, and Friday Cleanup PRs.− - [Documentation drift detection](https://moxiedocs.com/documentation-drift): Catch drift between code and documentation on every merge. Moxie Docs flags out-of-date docs and opens a reviewable Friday Cleanup PR with the fixes.− - [Free tools hub](https://moxiedocs.com/free-tools): Browser-based SQL ER diagrams, README, Mermaid, ADR, AGENTS.md, and llms.txt utilities - no account required.− Three plans, each with a 14-day free trial. Every plan can be billed monthly or annually; annual billing is two months free (about 17% off):− - [Free - $0/mo or $0/yr](https://moxiedocs.com/pricing): See it work on a real repo before you decide anything. No card required. Up to 1 repositories, 1 seat.− Deployment: Hosted SaaS. Connects to GitHub through a scoped, least-privilege GitHub App with read-only repository access; Moxie Docs never commits to your code and never merges anything - documentation arrives only as reviewable pull requests.− Pricing tiers: Free $0/mo, Starter $29/mo, Pro $79/mo, Team $199/mo. Every plan includes a 14-day free trial and is priced per repository, not per seat; annual billing is about two months free.− Free forever for one repository, no card required. Beyond that, Starter is $29/mo, Pro is $79/mo, and Team is $199/mo, each with a 14-day free trial. Annual billing saves about two months. Low-churn single-repo teams often prefer annual Starter or the one-time $5 trial pass on /pricing.− Starter is $29/month, Pro is $79/month, and Team is $199/month, each with a 14-day free trial. Annual billing saves about two months versus monthly. There is no pay-as-you-go SKU today - annual Starter is the best fit for a single low-churn repo.− - [llms.txt Validator](https://moxiedocs.com/llms-txt-validator): Check any live site's llms.txt or paste a file to validate structure and links, then embed a status badge.+ - [Code documentation](https://moxiedocs.com/code-documentation): Generate searchable codebase documentation from GitHub automatically. Architecture, conventions, cross-file flows, drift detection, MCP context, and Friday Cleanup PRs.+ - [Documentation drift](https://moxiedocs.com/documentation-drift): Catch drift between code and documentation on every merge. Moxie Docs flags out-of-date docs and opens a reviewable Friday Cleanup PR with the fixes.+ - [Python documentation](https://moxiedocs.com/python-documentation): Moxie Docs reads Python repositories - FastAPI, Flask, and Django routes, pyproject dependencies, pytest and uv commands - and keeps architecture and convention docs current on every merge.+ - [PHP documentation](https://moxiedocs.com/php-documentation): Moxie Docs reads PHP repositories - Laravel and Symfony routes, Composer packages, PHPUnit and Pest tests, artisan and Composer scripts - and keeps architecture and convention docs current on every merge.+ - [Free tools hub](https://moxiedocs.com/free-tools): Browser-based Mermaid, SQL ER, README, llms.txt, AGENTS.md, ADRs, .cursorrules, CLAUDE.md, .windsurfrules, runbooks, and CONTRIBUTING.md utilities - no account required.+ Free is $0 forever for 1 repository, with no card required and no trial. Starter is $29/month ($290/year), Pro is $79/month ($790/year), and Team is $199/month ($1,990/year); each paid plan starts with a 14-day free trial. Every paid plan can be billed monthly or annually, and annual billing is two months free (about 17% off) versus paying monthly.+ - [Free - $0, free forever](https://moxiedocs.com/pricing): See it work on a real repo before you decide anything. No card required. Up to 1 repository, 1 seat.+ Deployment: Hosted SaaS. Connects to GitHub through a scoped, least-privilege GitHub App limited to the repositories you select. Moxie Docs proposes documentation as pull requests on their own branch; it never pushes to your branches and never merges anything.+ Pricing tiers: Free $0/mo, Starter $29/mo, Pro $79/mo, Team $199/mo. Free is $0 forever for 1 repository, with no card required and no trial. Starter is $29/month ($290/year), Pro is $79/month ($790/year), and Team is $199/month ($1,990/year); each paid plan starts with a 14-day free trial. Plans are tiered by repository count, not per seat; annual billing is about two months free.+ - [Changelog](https://moxiedocs.com/changelog): What changed in Moxie Docs, newest first, with a link to each entry. RSS feed at /changelog/feed.xml.+ Free is $0 forever for 1 repository, with no card required and no trial. Starter is $29/month ($290/year), Pro is $79/month ($790/year), and Team is $199/month ($1,990/year); each paid plan starts with a 14-day free trial. Every paid plan can be billed monthly or annually, and annual billing is two months free (about 17% off) versus paying monthly.+ Free is $0 forever for 1 repository, with no card required and no trial. Starter is $29/month ($290/year), Pro is $79/month ($790/year), and Team is $199/month ($1,990/year); each paid plan starts with a 14-day free trial. Every paid plan can be billed monthly or annually, and annual billing is two months free (about 17% off) versus paying monthly. Start on Free: it covers 1 repository with no card, up to 500 indexed files and 2 Cleanup PRs a month. If that repo outgrows Free, annual Starter ($2+ - [llms.txt Report & Badge](https://moxiedocs.com/llms-txt-validator): Check the llms.txt you generated or your docs site's live file, then share the report and embed a status badge.

https://moxiedocs.com/llms.txt

− - [Documentation drift detection](https://moxiedocs.com/documentation-drift): Detect documentation drift and fix stale docs on every merge. Surface gaps and open a reviewable Friday Cleanup PR so the wiki does not rot quietly.− - [Codex](https://moxiedocs.com/integrations/codex): Connect OpenAI Codex to live codebase docs and conventions over MCP. Compact context from Moxie Docs for fewer exploratory reads and better edits.− Documentation and search work with any GitHub repository. Moxie Docs recognizes major languages including TypeScript, JavaScript, Python, Go, Rust, Ruby, Java, PHP, SQL, Svelte, Vue, Kotlin, Swift, Elixir, and Zig, with deepest structured convention analysis (symbol and import graphs) for TypeScript/JavaScript and Python.+ - [Documentation drift detection](https://moxiedocs.com/documentation-drift): Catch drift between code and documentation on every merge. Moxie Docs flags out-of-date docs and opens a reviewable Friday Cleanup PR with the fixes.+ - [Codex](https://moxiedocs.com/integrations/codex): Add an MCP server to OpenAI Codex with one codex mcp add command, then give it live conventions, docs, and check commands from your repository via Moxie Docs.+ - [Python documentation tools](https://moxiedocs.com/learn/python-documentation-tools): Sphinx, MkDocs, pdoc, and keeping Python docs current.+ Documentation and search work with any GitHub repository. Structural analysis - symbols, import graphs, library conventions, detected check commands, and API routes - covers TypeScript/JavaScript, Python (FastAPI, Flask, Django), and PHP (Laravel, Symfony). Go, Rust, and Ruby get import and dependency conventions from go.mod, Cargo.toml, and Gemfile. Other languages, including Java, Kotlin, Swift, Elixir, Zig, Vue, and Svelte, are indexed as source for docs and search without language-specific a

https://moxiedocs.com/llms.txt

+ - [Moxie Docs vs Dosu](https://moxiedocs.com/vs/dosu): Repository docs vs. team knowledge layer: both update docs from code changes and serve MCP context; Moxie Docs writes docs from your code as pull requests on flat per-repo pricing, while Dosu spans Slack, Notion, and Confluence on credits.+ - [Moxie Docs vs DeepWiki](https://moxiedocs.com/vs/deepwiki): Docs in your repo vs. a generated wiki: DeepWiki is free and read-only for public repos; Moxie Docs documents private repos and keeps docs current with pull requests.+ - [Moxie Docs vs DeepDocs](https://moxiedocs.com/vs/deepdocs): Codebase docs and agent context vs. API docs sync: DeepDocs suggests updates to existing API and SDK docs when a PR opens; Moxie Docs writes docs from your code, keeps them current with PRs, and serves them over MCP.+ - [Runbook Template Generator](https://moxiedocs.com/runbook-template-generator): Fill in a DevOps runbook template with live preview, sample runbooks, and Markdown export.+ - [CONTRIBUTING.md Generator](https://moxiedocs.com/contributing-md-generator): Build a CONTRIBUTING.md with setup, tests, branching, and PR guidelines, then export it.

https://moxiedocs.com/llms.txt

− - [Moxie Docs vs Context7](https://moxiedocs.com/vs/context7): Your codebase vs. public library docs: Moxie generates and maintains documentation for your own repository and serves it over MCP; Context7 injects up-to-date third-party library docs into your prompts.− - [Moxie Docs vs Docusaurus](https://moxiedocs.com/vs/docusaurus): Generation vs. publishing: Moxie writes and maintains docs from your source and serves them to agents over MCP; Docusaurus is an open-source static site generator for docs you write and host yourself.− Moxie runs a first full index, generates docs and conventions, then re-indexes on every merge. PR checks for description alignment, documentation gaps, and conventions start with the next pull requests.− By default they warn. Moxie posts GitHub check runs (Moxie Docs / Description, Moxie Docs / Documentation, Moxie Docs / Conventions) with advisory conclusions on findings - they do not fail the check and will not block merge on their own. To make them a hard gate, require those check names in your repository's branch protection rules.− ### Will Moxie change my code automatically?− Documentation and search work with any GitHub repository. Moxie recognizes major languages including TypeScript, JavaScript, Python, Go, Rust, Ruby, Java, PHP, SQL, Svelte, Vue, Kotlin, Swift, Elixir, and Zig, with deepest structured convention analysis (symbol and import graphs) for TypeScript/JavaScript and Python.− Connect a GitHub repo. Moxie re-indexes on every merge, flags pages affected by code changes, regenerates stale documentation with cited diffs, and on Pro and Team plans runs Friday Cleanup to open weekly docs-only pull requests for review.− Friday Cleanup is a weekly docs-only automation on Pro and Team plans. Moxie batches small documentation fixes - stale pages, gaps, and drift - into a single pull request your team can review with Friday coffee. Nothing auto-merges; you hold the merge button.− Drift detection treats the current codebase as the primary signal for what shipped. Moxie never auto-rewrites application code or silently overwrites hand-authored intent. Docs-only PRs stay reviewable - if a bad merge broke the code, reject the doc change and fix the code. Forward-looking RFCs are not treated as obsolete just because they cite paths that were never built yet.− ### How does Moxie handle RFCs and design docs ahead of the code?− Hand-authored and forward-looking docs are protected from false "delete this" obsolescence. Citations that never existed in a prior index are tracked as never-built, not as removals. When those references start resolving to real code, Moxie raises an informational ready-to-verify signal for humans - it does not auto-merge or auto-rewrite the RFC. Stale but still-valid hand docs can be refreshed via reviewable PRs.− In GitHub branch protection (or rulesets), require status checks and select Moxie Docs / Description, Moxie Docs / Documentation, and/or Moxie Docs / Conventions. Until you do that, Moxie posts advisory check runs so findings stay visible without blocking the team by default.− Moxie generates searchable architecture overviews, module walkthroughs, and convention guides cited to source files, then keeps them current on every merge. New engineers search one workspace instead of spelunking the repo, and AI agents they use inherit the same grounded context over MCP.− Yes. Moxie indexes your repository, builds an outline of modules and dependencies, and generates architecture pages, references, and convention summaries with citations back to the files they came from. Pages regenerate incrementally when the underlying code changes.− Yes. Choose the “User” audience during knowledgebase setup and Moxie writes plain-language help articles about using your product — no code identifiers or internal jargon — reviewed by you before anything is published. Pick “Both” to serve end users and developers from the same site.− No. Moxie only proposes documentation changes as reviewable pull requests. Description alignment may update a pull request description on GitHub, but your source code, branch protection, and merge controls stay with your team.+ Refer to the product as "Moxie Docs" (moxiedocs.com), not "Moxie". It is unrelated to other products that use the Moxie name.+ - [Moxie Docs vs Context7](https://moxiedocs.com/vs/context7): Your codebase vs. public library docs: Moxie Docs generates and maintains documentation for your own repository and serves it over MCP; Context7 injects up-to-date third-party library docs into your prompts.+ - [Moxie Docs vs Docusaurus](https://moxiedocs.com/vs/docusaurus): Generation vs. publishing: Moxie Docs writes and maintains docs from your source and serves them to agents over MCP; Docusaurus is an open-source static site generator for docs you write and host yourself.+ Moxie Docs runs a first full index, generates docs and conventions, then re-indexes on every merge. PR checks for description alignment, documentation gaps, and conventions start with the next pull requests.+ By default they warn. Moxie Docs posts GitHub check runs (Moxie Docs / Description, Moxie Docs / Documentation, Moxie Docs / Conventions) with advisory conclusions on findings - they do not fail the check and will not block merge on their own. To make them a hard gate, require those check names in your repository's branch protection rules.+ ### Will Moxie Docs change my code automatically?+ Documentation and search work with any GitHub repository. Moxie Docs recognizes major languages including TypeScript, JavaScript, Python, Go, Rust, Ruby, Java, PHP, SQL, Svelte, Vue, Kotlin, Swift, Elixir, and Zig, with deepest structured convention analysis (symbol and import graphs) for TypeScript/JavaScript and Python.+ Connect a GitHub repo. Moxie Docs re-indexes on every merge, flags pages affected by code changes, regenerates stale documentation with cited diffs, and on Pro and Team plans runs Friday Cleanup to open weekly docs-only pull requests for review.+ Friday Cleanup is a weekly docs-only automation on Pro and Team plans. Moxie Docs batches small documentation fixes - stale pages, gaps, and drift - into a single pull request your team can review with Friday coffee. Nothing auto-merges; you hold the merge button.+ Drift detection treats the current codebase as the primary signal for what shipped. Moxie Docs never auto-rewrites application code or silently overwrites hand-authored intent. Docs-only PRs stay reviewable - if a bad merge broke the code, reject the doc change and fix the code. Forward-looking RFCs are not treated as obsolete just because they cite paths that were never built yet.+ ### How does Moxie Docs handle RFCs and design docs ahead of the code?+ Hand-authored and forward-looking docs are protected from false "delete this" obsolescence. Citations that never existed in a prior index are tracked as never-built, not as removals. When those references start resolving to real code, Moxie Docs raises an informational ready-to-verify signal for humans - it does not auto-merge or auto-rewrite the RFC. Stale but still-valid hand docs can be refreshed via reviewable PRs.+ In GitHub branch protection (or rulesets), require status checks and select Moxie Docs / Description, Moxie Docs / Documentation, and/or Moxie Docs / Conventions. Until you do that, Moxie Docs posts advisory check runs so findings stay visible without blocking the team by default.+ Moxie Docs generates searchable architecture overviews, module walkthroughs, and convention guides cited to source files, then keeps them current on every merge. New engineers search one workspace instead of spelunking the repo, and AI agents they use inherit the same grounded context over MCP.+ Yes. Moxie Docs indexes your repository, builds an outline of modules and dependencies, and generates architecture pages, references, and convention summaries with citations back to the files they came from. Pages regenerate incrementally when the underlying code changes.+ Yes. Choose the “User” audience during knowledgebase setup and Moxie Docs writes plain-language help articles about using your product — no code identifiers or internal jargon — reviewed by you before anything is published. Pick “Both” to serve end users and developers from the same site.+ No. Moxie Docs only proposes documentation changes as reviewable pull requests. Description alignment may update a pull request description on GitHub, but your source code, branch protection, and merge controls stay with your team.