Skip to content

docs: Add FAQ section#28

Open
meichuanyi wants to merge 1 commit into
NirDiamant:mainfrom
meichuanyi:main
Open

docs: Add FAQ section#28
meichuanyi wants to merge 1 commit into
NirDiamant:mainfrom
meichuanyi:main

Conversation

@meichuanyi

@meichuanyi meichuanyi commented May 18, 2026

Copy link
Copy Markdown

Adds a comprehensive FAQ section covering:

  • What is the Controllable RAG Agent
  • How it differs from traditional RAG systems
  • Key features (Deterministic graph, Hallucination prevention, Multi-step reasoning)
  • Agent workflow explanation
  • Evaluation metrics (Ragas)
  • Complex question handling example
  • LLM providers supported
  • Getting started
  • Custom dataset usage
  • Hallucination prevention mechanism
  • Anonymization technique
  • Related tutorials
  • License (Apache 2.0)
  • Help resources

This FAQ helps users quickly understand the agent's sophisticated reasoning capabilities.

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive FAQ section to help address common user questions about the Controllable RAG Agent, including detailed answers on key features, differences from traditional RAG systems, setup instructions, supported LLM providers, working with custom datasets, hallucination prevention strategies, anonymization techniques, evaluation metrics, and additional learning resources.

Review Change Stack

@coderabbitai

coderabbitai Bot commented May 18, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

A new FAQ section has been added to README.md with 14 Q&A entries covering the Controllable RAG Agent's purpose, technical approach, features, operational mechanics, evaluation methods, provider support, setup instructions, dataset customization, verification behavior, anonymization technique, related resources, licensing, and support channels.

Changes

FAQ Documentation Addition

Layer / File(s) Summary
FAQ section content
README.md
New FAQ section (lines 186–305) introduces 14 question-answer pairs explaining agent overview, differences from traditional RAG, key features, operational workflow, evaluation metrics, supported LLM providers, setup guidance, custom dataset usage, hallucination prevention, anonymization, related repositories, MIT license terms, and support contact information.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A FAQ blooms in the README's garden,
Fourteen questions answered with clarity—
What, why, how, and where to start,
No code to change, just knowledge shared bright! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: Add FAQ section' clearly and accurately describes the main change—adding a FAQ section to the documentation. It is concise, specific, and directly related to the primary modification in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 259-263: Update the README so the "Getting-started" steps and the
`.env` example are consistent: add the missing ANTHROPIC_API_KEY (or other LLM
provider keys you mention) to the `.env` example that currently shows
OPENAI_API_KEY and GROQ_API_KEY, or conversely only list OPENAI_API_KEY and
GROQ_API_KEY in the setup steps; ensure the unique env var names OPENAI_API_KEY,
GROQ_API_KEY and ANTHROPIC_API_KEY are explicitly listed and documented together
so first-time setup and the `.env` example match.
- Around line 251-255: README inconsistency: unify framework and provider setup
by clarifying whether the project uses LangGraph or LangChain (update the
sentence "The agent is built on LangGraph" or the technologies list to match the
actual implementation), and align the environment setup to advertise supported
providers by adding instructions for Anthropic and local models: document
required env vars (e.g., ANTHROPIC_API_KEY, OLLAMA_HOST/OLLAMA_API_KEY or
equivalent) and how to enable local providers (Ollama) alongside OPENAI_API_KEY
and GROQ_API_KEY; update the sentences listing supported providers ("OpenAI",
"Anthropic", "Local models", "Any LangChain-compatible provider") so they match
the setup section and include short notes on how to configure each provider.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a48e0328-3428-4c9c-be38-f977582aca14

📥 Commits

Reviewing files that changed from the base of the PR and between c75e564 and 97adb8f.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
Comment on lines +251 to +255
The agent is built on LangGraph and supports:
- **OpenAI** — GPT-4, GPT-3.5
- **Anthropic** — Claude models
- **Local models** — Via Ollama or other local LLM providers
- **Any LangChain-compatible provider**

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify framework/provider claims in README for consistency.
rg -n -C2 'LangGraph|LangChain|Anthropic|OpenAI|GROQ|Ollama|API_KEY' README.md

Repository: NirDiamant/Controllable-RAG-Agent

Length of output: 1662


Align LangGraph/LangChain terminology and provider setup instructions in README.

Line 251 claims the agent is built on LangGraph, but line 147 lists LangChain in technologies. Additionally, lines 252–255 advertise support for Anthropic and local models, yet the setup instructions (lines 116–117) only show OPENAI_API_KEY and GROQ_API_KEY. Line 261 mentions Anthropic key setup without providing guidance. Clarify which framework is used and ensure setup instructions match the advertised provider support.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 251 - 255, README inconsistency: unify framework and
provider setup by clarifying whether the project uses LangGraph or LangChain
(update the sentence "The agent is built on LangGraph" or the technologies list
to match the actual implementation), and align the environment setup to
advertise supported providers by adding instructions for Anthropic and local
models: document required env vars (e.g., ANTHROPIC_API_KEY,
OLLAMA_HOST/OLLAMA_API_KEY or equivalent) and how to enable local providers
(Ollama) alongside OPENAI_API_KEY and GROQ_API_KEY; update the sentences listing
supported providers ("OpenAI", "Anthropic", "Local models", "Any
LangChain-compatible provider") so they match the setup section and include
short notes on how to configure each provider.

Comment thread README.md
Comment on lines +259 to +263
1. Clone the repository
2. Install dependencies: `pip install -r requirements.txt`
3. Set up your LLM API keys (OpenAI, Anthropic, etc.)
4. Prepare your PDF documents
5. Run the agent with your custom questions

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Getting-started keys don’t match the documented .env example.

Line 261 tells users to set OpenAI/Anthropic keys, but the setup block (Lines 116-118) only shows OPENAI_API_KEY and GROQ_API_KEY. Please make these sections consistent so first-time setup doesn’t fail.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 259 - 263, Update the README so the "Getting-started"
steps and the `.env` example are consistent: add the missing ANTHROPIC_API_KEY
(or other LLM provider keys you mention) to the `.env` example that currently
shows OPENAI_API_KEY and GROQ_API_KEY, or conversely only list OPENAI_API_KEY
and GROQ_API_KEY in the setup steps; ensure the unique env var names
OPENAI_API_KEY, GROQ_API_KEY and ANTHROPIC_API_KEY are explicitly listed and
documented together so first-time setup and the `.env` example match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant