Docs Knowledge Assistant is an Eve agent that Answers from your repo docs and cites the file. It is for Eve developers answering product questions. Preview every file on this page, then install with npx shadcn@latest add @evex/docs-knowledge-assistant. Docs Knowledge Assistant is an eve agent that answers questions from the installing repository's documentation files.
Answers from your repo docs and cites the file.
Docs Knowledge Assistant is an eve agent that answers questions from the installing repository's documentation files. It searches README, docs/, CONTRIBUTING*, and AGENTS.md, then replies with file-path citations so readers can verify the source.
You interact with it through Eve chat sessions or by mentioning it on a GitHub issue comment. It ignores pull request conversations, never publishes GitHub PR reviews, and never applies taxonomy labels or triage other issues.
When the documentation clearly lacks an answer, it says so. On GitHub issue-comment turns it can optionally open a documentation-gap issue with open_docs_issue so maintainers can track missing docs without turning the agent into a second issue bot.
New contributors ask how to install or configure the project in Eve chat. The agent reads README.md or docs/install.md and answers with the cited path instead of guessing from source.
Mention the bot on an issue asking about contribution steps. It answers from CONTRIBUTING* or AGENTS.md and posts the cited reply on the issue timeline.
When someone asks about on-call policy or an undocumented API, the agent says the docs do not cover it rather than inventing steps from application source.
When a recurring question on a GitHub issue has no docs home, open_docs_issue creates a focused documentation issue so maintainers can fill the gap without labeling or triaging other work.
Run npx shadcn@latest add @evex/docs-knowledge-assistant inside an eve app, set AI_GATEWAY_API_KEY, then ask documentation questions in Eve chat. For GitHub issue replies, deploy over HTTPS, create a GitHub App pointing at /eve/v1/github, and mention the bot on an issue.
No. The channel ignores pull request conversations, there is no PR review publication path, and it never applies taxonomy labels. Use @evex/code-reviewer for PR reviews and @evex/github-issue-maintainer for issue triage.
Only README*, docs/**, CONTRIBUTING*, and AGENTS.md. search_docs and read_doc refuse application source, tests, and config paths.
The agent says the documentation does not cover the question. On GitHub issue-comment turns, when the gap is clear, it can call open_docs_issue to create a documentation issue without labeling other issues. Eve chat refuses that tool.
No. Chat works with only AI_GATEWAY_API_KEY. GitHub App credentials are needed only for issue-comment Q&A and optional docs-gap issue creation.
npx shadcn@latest add @evex/docs-knowledge-assistant