Finds stale product docs and drafts updates with file cites.
Full install guide: Install an Eve agent.
Knowledge Base Gardener is an Eve agent that reads docs on disk and drafts a cited update you review. It is for Eve developers answering product questions. Preview every file on this page, then install with npx shadcn@latest add @evex/knowledge-base-gardener. After install you own the files.
Paste the stale page or changelog you want reconciled. Knowledge Base Gardener searches the local product-docs tree, reads the matching files, and writes a draft with file-path citations. Nothing is committed or overwritten. Copy the draft from the session, then you review and apply it.
You interact with it through Eve chat sessions only. There is no GitHub channel and no publish connection. Paste a gardening request or a suspected stale page, get a draft, then copy the update into your docs yourself. The agent never applies the edit.
The draft_doc_update tool records the proposed text and citations and always reports published false so the agent never claims the docs were shipped. When a cited page looks current, it says so instead of inventing churn from training data.
An operator pastes a help article that still says a refund window is coming soon. The agent cites docs/help/billing.md, drafts replacement copy, and stops so a human can apply the edit.
A page still tells readers to ignore an old sentence after a TODO. The agent drafts a cleaned update from that file only and keeps the path in the draft.
When the cited product docs already match the request, the agent says the page looks current instead of inventing a rewrite from training data.
After draft_doc_update returns, the operator can ask the agent to write_file the update into a local path for review or handoff without implying the docs were published.
Run npx shadcn@latest add @evex/knowledge-base-gardener inside an eve app, set AI_GATEWAY_API_KEY and PRODUCT_DOCS_ROOTS, then paste a gardening request in Eve chat. Copy the returned draft into your docs yourself.
No. There is no publish tool and no GitHub channel. draft_doc_update always returns published false. Asking it to ship the page or open a pull request still produces a draft only.
Only paths under PRODUCT_DOCS_ROOTS. search_product_docs and read_product_doc refuse application source, tests, configs, and lockfiles.
The agent says the cited product docs look current and does not invent churn. It may still call draft_doc_update with staleFound set to false.
Support Reply Draft writes a customer-facing reply from help docs. This agent drafts a documentation update for a stale product page and still stops at the draft.
npx shadcn@latest add @evex/knowledge-base-gardener