Skip to content

Conversation

@davidmyriel
Copy link
Contributor

  • fix grammar, spelling and semantics
  • update headings
  • add new copy to mirror website copy
  • update product names

@pull-checklist
Copy link

Please make sure all the checkboxes are checked:

  • I have tested these changes locally.
  • I have reviewed the code changes.
  • I have added end-to-end and unit tests (if applicable).
  • I have updated the documentation and README.md file (if necessary).
  • I have removed unnecessary code and debug statements.
  • PR title is clear and follows the convention.
  • I have tagged reviewers or team members for feedback.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 30, 2025

Walkthrough

This PR rewrites README.md: updates branding and badges, reorganizes sections (About, Get Started split into OSS vs Cloud, Quickstart/Usage, Demos & Examples, Community & Support), replaces examples/CLI with new API names/flow (cognify, memify, add, search), and adjusts links and citation. (33 words)

Changes

Cohort / File(s) Summary
README rewrite
README.md
Full README overhaul: updated hero tagline and badges; restructured and renamed sections (About; Get Started → OSS vs Cloud; Quickstart/Usage; Demos & Examples; Community & Support); replaced code and CLI examples with new API names/flow (cognify, memify, add, search); updated links, demo URLs, and BibTeX citation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verify example code/CLI commands reflect actual API names and behavior.
  • Validate external links, Docs paths, and demo URLs.
  • Confirm citation/BibTeX formatting and badge text.

Possibly related PRs

Suggested labels

run-checks

Suggested reviewers

  • Vasilije1990
  • borisarzentar

Poem

🐇 I hopped through lines and trimmed each clause,
New taglines shining, tidy without pause.
Snippets aligned, links set to play,
Memory pipelines ready to stay.
— A rabbit nibbling docs, hooray! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The pull request description is largely incomplete when compared against the repository's template. The author provided only four brief bullet points describing the changes without addressing the required template sections: no Type of Change classification is selected, no Pre-submission Checklist items are verified, and no DCO Affirmation is included. While the bullet points do provide human-generated context about the updates (fixing grammar/spelling/semantics, updating headings, adding copy to mirror website, and updating product names), these do not constitute a mostly complete description following the template structure. The description should be expanded to follow the pull request template by adding a Type of Change section with an appropriate selection (likely "Documentation update"), completing the Pre-submission Checklist by checking the relevant items, and including the DCO Affirmation. The description itself could also be expanded from bullet points into a more comprehensive explanation of the reasoning behind these README changes.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (1 passed)
Check name Status Explanation
Title Check ✅ Passed The pull request title "docs: Fix Readme Instructions" is clearly related to the changeset, which consists entirely of README.md updates. The title correctly identifies this as a documentation change and accurately reflects that the PR addresses README content. While the actual changes extend beyond just "fixing" to include significant restructuring, branding updates, new sections, and content reorganization to mirror website copy, the title is not misleading and appropriately conveys the primary change to documentation.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0427586 and e69ff7c.

📒 Files selected for processing (1)
  • README.md (5 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[grammar] ~66-~66: Ensure spelling is correct
Context: ... width="50%" /> ## About Cognee Cognee is an open-source tool and platfo...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~199-~199: Using many exclamation marks might seem excessive (in this case: 7 exclamation marks for a text that’s 4250 characters long)
Context: ...welcome contributions from the community! Your input helps make Cognee better for...

(EN_EXCESSIVE_EXCLAMATION)

🔇 Additional comments (7)
README.md (7)

8-8: Header and branding updates look solid.

Tagline refresh, link reorganization, and badge caption corrections are all accurate and well-executed. The addition of the Docs link improves discoverability, and the "Community Plugins & Add-ons" label clarifies the repository's purpose.

Also applies to: 13-21, 28-28


44-44: Updated value proposition is clearer and better differentiates the product.

The new introductory statement (ECL pipelines vs. RAG) and language link formatting are appropriate and align well with the new branding and API updates.

Also applies to: 52-52


89-177: Quickstart section and code examples are comprehensive and well-formatted.

All code blocks now have proper language identifiers (resolving past MD040 linter violations). The progression from prerequisites through installation, configuration, and example usage is logical. API naming (cognify, memify, add, search) is consistent throughout, and the CLI alternative provides good flexibility for users. Python and bash syntax are correct.

Please verify that the API method names (cognify, memify, add, search, delete) match the current codebase implementation to ensure the examples run without errors.


179-203: Demos & Examples and Community & Support sections are well-organized.

The restructured demo section with consistent "Watch Demo" formatting improves discoverability, and the Community & Support framing is more welcoming than the previous labels. Links are properly formatted and the content flows logically.


205-218: Research & Citation section is properly formatted and enhances project credibility.

The renamed heading better reflects the content, and the BibTeX entry is correctly formatted with proper bibtex language identifier. The research paper citation adds academic rigor to the project documentation.


1-218: Overall: Documentation update is comprehensive and addresses all past review concerns.

All previously flagged critical issues have been resolved:

  • Empty and malformed links (lines 72-73, 91) are now properly formatted with correct URLs
  • "open-source" hyphenation is correct (line 68)
  • All code blocks now have proper language identifiers (resolving MD040 linting)

The restructuring successfully achieves the stated PR objectives—grammar/spelling corrections, heading updates, product name changes, and website-aligned copy. The new "About Cognee," "Quickstart," "Demos & Examples," and "Community & Support" organization is clearer and more user-friendly than the previous layout.

Minor note: Static analysis flags excessive exclamation marks in the document. The current usage (particularly at line 199) is contextually appropriate for an encouraging tone, but you may consider reviewing the overall punctuation style if consistency is a concern.

Please verify that all documentation and external URLs (particularly https://docs.cognee.ai/* paths) are active and point to the correct pages in the live documentation site, and confirm the API method names match the current codebase implementation.


66-88: About Cognee section is well-structured with clear OSS vs. Cloud differentiation.

Past critical issues (empty links, malformed syntax) have been fully resolved. Feature descriptions are compelling and properly highlight the distinctions between self-hosted and managed offerings. All documentation and platform URLs are active and accessible (verified: 200 OK for installation link, 307 redirects for platform URLs indicating normal routing behavior).


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.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Hello @davidmyriel, thank you for submitting a PR! We will respond as soon as possible.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7743071 and 7ee6cc8.

📒 Files selected for processing (1)
  • README.md (5 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[grammar] ~76-~76: Ensure spelling is correct
Context: ...ree/main/cognee-starter-kit) ## About Cognee Cognee transforms your data into a livin...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~215-~215: Using many exclamation marks might seem excessive (in this case: 7 exclamation marks for a text that’s 4029 characters long)
Context: ...welcome contributions from the community! Your input helps make Cognee better for...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
README.md

179-179: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔇 Additional comments (3)
README.md (3)

1-66: Navigation and messaging updates look good.

The title, tagline, and navigation links have been refreshed to better communicate the product's value proposition. All links are properly formatted and the section hierarchy is clear.


69-95: Quickstart and About sections are well-organized.

The renamed "Quickstart" section with bullet items provides clear entry points for users, and the revised "About Cognee" section effectively communicates key product features and deployment options.


183-234: Cognee Cloud, Community, and citation sections look good.

The restructured Demos & Examples, Community & Support, and Research & Citation sections are well-formatted and clearly presented. All links are properly formatted.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7ee6cc8 and 79f5201.

📒 Files selected for processing (1)
  • README.md (5 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[grammar] ~66-~66: Ensure spelling is correct
Context: ... width="50%" /> ## About Cognee Cognee is an open source tool and platfo...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~68-~68: Use a hyphen to join words.
Context: ...div> ## About Cognee Cognee is an open source tool and platform that transforms...

(QB_NEW_EN_HYPHEN)


[style] ~97-~97: Consider using the synonym “brief” (= concise, using a few words, not lasting long) to strengthen your wording.
Context: ...p=sharing) ## Quickstart Let’s take a quick look at how Cognee works in just a few ...

(QUICK_BRIEF)


[style] ~198-~198: Using many exclamation marks might seem excessive (in this case: 7 exclamation marks for a text that’s 4153 characters long)
Context: ...welcome contributions from the community! Your input helps make Cognee better for...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
README.md

72-72: No empty links

(MD042, no-empty-links)


155-155: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


163-163: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


174-174: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔇 Additional comments (3)
README.md (3)

1-31: Navigation and branding updates look good.

The hero tagline, navigation links, and badge updates are well-executed and improve clarity around product positioning.


44-58: Updated value proposition is clear and well-positioned.

The new introductory copy effectively communicates the ECL pipeline concept and differentiator. Language links are properly maintained.


178-217: Demos, Community, and Citation sections are well-structured.

The reorganization of demos with clear headings, the new Community & Support section with clear calls-to-action, and the Research & Citation section with proper BibTeX formatting all follow documentation best practices.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

♻️ Duplicate comments (1)
README.md (1)

66-93: Fix empty and malformed links; apply hyphenation to "open source".

Three critical Markdown syntax issues and one styling issue prevent correct rendering:

  1. Line 68: "open source" should be hyphenated as "open-source" for proper compound adjective styling.
  2. Line 72: Empty link—[]() has no href; add the documentation URL for the Self-host option.
  3. Line 73: Double opening parenthesis in the Cognee Cloud link—((https://...)) is malformed; should be (https://...).
  4. Line 91: Double opening parenthesis in the Colab walkthrough link—same syntax error; should be (https://...).

Apply this diff:

-Cognee is an open source tool and platform that transforms your raw data into persistent and dynamic AI memory for Agents. It combines vector search with graph databases to make your data both searchable by meaning and connected by relationships. 
+Cognee is an open-source tool and platform that transforms your raw data into persistent and dynamic AI memory for Agents. It combines vector search with graph databases to make your data both searchable by meaning and connected by relationships. 
 
 You can use Cognee in two ways:
 
-1. [Self-host Cognee Open Source](), which stores all data locally by default.
-2. [Connect to Cognee Cloud]((https://platform.cognee.ai/)), and get the same OSS stack on managed infrastructure for easier development and productionization.
+1. [Self-host Cognee Open Source](https://docs.cognee.ai/getting-started/installation/), which stores all data locally by default.
+2. [Connect to Cognee Cloud](https://platform.cognee.ai/), and get the same OSS stack on managed infrastructure for easier development and productionization. 
 
 ### Cognee Open Source (self-hosted):
 ...
-To learn more, [check out this short, end-to-end Colab walkthrough]((https://colab.research.google.com/drive/12Vi9zID-M3fpKpKiaqDBvkk98ElkRPWy?usp=sharing)) of Cognee's core features.
+To learn more, [check out this short, end-to-end Colab walkthrough](https://colab.research.google.com/drive/12Vi9zID-M3fpKpKiaqDBvkk98ElkRPWy?usp=sharing) of Cognee's core features.

Note: The href placeholder https://docs.cognee.ai/getting-started/installation/ for the Self-host link should be updated to the correct documentation URL if different.

🧹 Nitpick comments (1)
README.md (1)

199-199: Consider moderating excessive exclamation marks.

Line 199 contains multiple exclamation marks in a short span ("...from the community! Your input helps make Cognee better for everyone."). While not a blocker, reducing exclamation mark density to one per message improves tone consistency and readability.

Consider softening to:

-We welcome contributions from the community! Your input helps make Cognee better for everyone.
+We welcome contributions from the community. Your input helps make Cognee better for everyone.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a068f35 and 3472f62.

📒 Files selected for processing (1)
  • README.md (5 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: topoteretes/cognee PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-27T09:21:14.154Z
Learning: Use clear, imperative PR titles (≤ 72 chars) with conventional commit style; CI validates semantic PR titles
🪛 LanguageTool
README.md

[grammar] ~66-~66: Ensure spelling is correct
Context: ... width="50%" /> ## About Cognee Cognee is an open source tool and platfo...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~68-~68: Use a hyphen to join words.
Context: ...div> ## About Cognee Cognee is an open source tool and platform that transforms...

(QB_NEW_EN_HYPHEN)


[style] ~199-~199: Using many exclamation marks might seem excessive (in this case: 7 exclamation marks for a text that’s 4205 characters long)
Context: ...welcome contributions from the community! Your input helps make Cognee better for...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
README.md

72-72: No empty links

(MD042, no-empty-links)

🔇 Additional comments (3)
README.md (3)

8-8: Well-executed branding and navigation updates.

The hero tagline, navigation links, and badge URLs have been appropriately refreshed to reflect the updated product messaging and documentation structure. The additions of "Docs" and "Learn More" links improve discoverability.

Also applies to: 13-15, 21-21, 28-28, 44-44, 52-52


95-177: Code blocks, examples, and Quickstart section are well-structured.

Language identifiers have been properly added to fenced code blocks (bash, text, ```python), enabling correct syntax highlighting. The Quickstart section provides clear prerequisites, installation steps, LLM configuration, and CLI usage with appropriate examples.


179-218: Demos, Community & Support, and Citation sections are well-organized.

The restructured sections ("Demos & Examples," "Community & Support," "Research & Citation") improve clarity and navigation. The content updates align with the PR objective of mirroring website copy and updating terminology.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

♻️ Duplicate comments (1)
README.md (1)

68-73: CRITICAL: Unresolved link issues from prior review—must be fixed before merge.

Three previously flagged Markdown link defects persist:

  1. Line 72: Empty link—[Self-host Cognee Open Source]() has no href; add a documentation URL.
  2. Line 73: Malformed syntax—[Connect to Cognee Cloud]((https://platform.cognee.ai/)) has double opening paren; remove one.
  3. Line 91: Malformed syntax—[check out this short, end-to-end Colab walkthrough]((https://... has double opening paren; remove one.
  4. Line 68: Style—"open source" should be hyphenated as "open-source" for proper grammatical styling.

Apply this diff:

-Cognee is an open source tool and platform that transforms your raw data into persistent and dynamic AI memory for Agents. It combines vector search with graph databases to make your documents both searchable by meaning and connected by relationships. 
+Cognee is an open-source tool and platform that transforms your raw data into persistent and dynamic AI memory for Agents. It combines vector search with graph databases to make your documents both searchable by meaning and connected by relationships. 
 
 You can use Cognee in two ways:
 
-1. [Self-host Cognee Open Source](), which stores all data locally by default.
-2. [Connect to Cognee Cloud]((https://platform.cognee.ai/)), and get the same OSS stack on managed infrastructure for easier development and productionization. 
+1. [Self-host Cognee Open Source](https://docs.cognee.ai/getting-started/installation/), which stores all data locally by default.
+2. [Connect to Cognee Cloud](https://platform.cognee.ai/), and get the same OSS stack on managed infrastructure for easier development and productionization. 

 To learn more, [check out this short, end-to-end Colab walkthrough](https://colab.research.google.com/drive/12Vi9zID-M3fpKpKiaqDBvkk98ElkRPWy?usp=sharing) of Cognee's core features.

Note: Update the href for the Self-host link if the documentation URL differs.

Also applies to: 91-91

🧹 Nitpick comments (1)
README.md (1)

199-199: Minor: Excessive exclamation mark density—consider moderating tone.

Line 199 contains 7 exclamation marks across 4,213 characters, flagging stylistic excess per LanguageTool. Reword one or two sentences to use periods or downgrade enthusiasm slightly for a more measured professional tone, e.g.:

-We welcome contributions from the community! Your input helps make Cognee better for everyone. See [`CONTRIBUTING.md`](CONTRIBUTING.md) to get started.
+We welcome contributions from the community. Your input helps make Cognee better for everyone. See [`CONTRIBUTING.md`](CONTRIBUTING.md) to get started.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3472f62 and 0427586.

📒 Files selected for processing (1)
  • README.md (5 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: topoteretes/cognee PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-27T09:21:14.154Z
Learning: Use clear, imperative PR titles (≤ 72 chars) with conventional commit style; CI validates semantic PR titles
🪛 LanguageTool
README.md

[grammar] ~66-~66: Ensure spelling is correct
Context: ... width="50%" /> ## About Cognee Cognee is an open source tool and platfo...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~68-~68: Use a hyphen to join words.
Context: ...div> ## About Cognee Cognee is an open source tool and platform that transforms...

(QB_NEW_EN_HYPHEN)


[style] ~199-~199: Using many exclamation marks might seem excessive (in this case: 7 exclamation marks for a text that’s 4213 characters long)
Context: ...welcome contributions from the community! Your input helps make Cognee better for...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
README.md

72-72: No empty links

(MD042, no-empty-links)

🔇 Additional comments (2)
README.md (2)

1-64: Branding and header restructuring looks solid.

Tagline updated ("Accurate & Persistent Memory for AI agents"), navigation reorganized (Docs and Learn More links added), community label clarified ("Community Plugins & Add-ons"), and badge metadata refreshed. These align well with the PR objectives.


44-44: Content and language refinements approved.

Core description now emphasizes ECL pipelines over RAG (line 44), and translation link corrected (line 52). Changes support the documentation update goals.

Also applies to: 52-52

@Vasilije1990 Vasilije1990 merged commit b1fdb71 into topoteretes:main Nov 1, 2025
2 of 3 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Nov 6, 2025
16 tasks
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.

2 participants