Skip to content

fix: resolve #100 — Add repository architecture map for new contributors#127

Open
andoan16 wants to merge 1 commit into
SahilKumar75:mainfrom
andoan16:contribai/improve/quality/add-repository-architecture-map-for-new-
Open

fix: resolve #100 — Add repository architecture map for new contributors#127
andoan16 wants to merge 1 commit into
SahilKumar75:mainfrom
andoan16:contribai/improve/quality/add-repository-architecture-map-for-new-

Conversation

@andoan16
Copy link
Copy Markdown

@andoan16 andoan16 commented May 30, 2026

Summary

fix: resolve #100 — Add repository architecture map for new contributors

Problem

Severity: Medium | File: README.md

Add a concise architecture map to help new contributors understand the project structure and where to make changes for different types of work (app, backend, ML worker, docs). The map should link to existing documentation rather than duplicating content, and be scannable for first-time contributors.

Solution

Add a new section titled "Repository Architecture" after the introduction in README.md. Include a brief description of each main directory (app, backend, ml-worker, docs) with their purposes, and link to the existing HLD, LLD, and contribution guide. Use bullet points or a simple diagram to show how these components interact. Keep the section under 10 lines for easy scanning.

Changes

  • README.md (modified)

Testing

  • Existing tests pass
  • Manual review completed
  • No new warnings/errors introduced

Summary by CodeRabbit

  • Documentation
    • Enhanced repository documentation with a structured "Repository Architecture" section that clearly outlines the project's top-level directory structure, providing clearer guidance for users navigating the codebase.

Review Change Stack

…ew contributors

Fixes SahilKumar75#100

Signed-off-by: Ân Đoàn <33853760+andoan16@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 30, 2026

📝 Walkthrough

Walkthrough

The README repository overview is restructured from an informal "3 working parts" description to a formal "Repository Architecture" section that documents the purpose and structure of each top-level directory (app/, backend/, ml-worker/, and docs/).

Changes

Repository Architecture Documentation

Layer / File(s) Summary
Repository directory structure and overview
README.md
README lines 8–13 introduce a labeled "Repository Architecture" section describing the purpose of top-level directories (app/, backend/, ml-worker/, docs/), replacing the previous informal description.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

  • #100: Directly addresses the objective to add a repository architecture map for new contributors by introducing a concise "Repository Architecture" section in the README with labeled directories and descriptions.

Poem

🐰 A map drawn plain, with labels clear,
For newcomers to find their way here,
App, backend, worker, docs all lined,
The rabbit hops through files designed. 🗺️

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: adding a repository architecture map for new contributors to resolve issue #100.
Description check ✅ Passed The PR description covers key sections with clear problem statement, solution, and testing checklist, though it deviates from the required template structure.
Linked Issues check ✅ Passed The PR directly addresses all requirements from issue #100: adds a repository architecture section identifying main directories, links to existing documentation, maintains conciseness for scanning, and is documentation-only.
Out of Scope Changes check ✅ Passed The PR contains only documentation changes to README.md and directly supports the linked issue objectives with no unrelated modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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.

Copy link
Copy Markdown

@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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
README.md (1)

40-48: ⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Fix absolute file paths that will break for other users.

Lines 40-48 contain hardcoded absolute paths (e.g., /Users/sahilkumarsingh/Desktop/SENTRI/docs/...) that only work on the author's machine. All other contributors will encounter broken links.

🔗 Proposed fix using relative paths
-- HLD: [docs/system-design-hld.md](/Users/sahilkumarsingh/Desktop/SENTRI/docs/system-design-hld.md)
-- LLD: [docs/system-design-lld.md](/Users/sahilkumarsingh/Desktop/SENTRI/docs/system-design-lld.md)
-- Home AI logic: [docs/ai-logic-home-timetable.md](/Users/sahilkumarsingh/Desktop/SENTRI/docs/ai-logic-home-timetable.md)
-- Myspace AI logic: [docs/ai-logic-myspace.md](/Users/sahilkumarsingh/Desktop/SENTRI/docs/ai-logic-myspace.md)
-- Myspace indexing pipeline: [docs/myspace-indexing-pipeline.md](/Users/sahilkumarsingh/Desktop/SENTRI/docs/myspace-indexing-pipeline.md)
-- Contribution workflow: [CONTRIBUTING.md](/Users/sahilkumarsingh/Desktop/SENTRI/CONTRIBUTING.md)
-- Code of conduct: [CODE_OF_CONDUCT.md](/Users/sahilkumarsingh/Desktop/SENTRI/CODE_OF_CONDUCT.md)
-- Security policy: [SECURITY.md](/Users/sahilkumarsingh/Desktop/SENTRI/SECURITY.md)
-- Support policy: [SUPPORT.md](/Users/sahilkumarsingh/Desktop/SENTRI/SUPPORT.md)
+- HLD: [docs/system-design-hld.md](docs/system-design-hld.md)
+- LLD: [docs/system-design-lld.md](docs/system-design-lld.md)
+- Home AI logic: [docs/ai-logic-home-timetable.md](docs/ai-logic-home-timetable.md)
+- Myspace AI logic: [docs/ai-logic-myspace.md](docs/ai-logic-myspace.md)
+- Myspace indexing pipeline: [docs/myspace-indexing-pipeline.md](docs/myspace-indexing-pipeline.md)
+- Contribution workflow: [CONTRIBUTING.md](CONTRIBUTING.md)
+- Code of conduct: [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)
+- Security policy: [SECURITY.md](SECURITY.md)
+- Support policy: [SUPPORT.md](SUPPORT.md)
🤖 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 40 - 48, The README contains hardcoded absolute file
paths for links (e.g., docs/system-design-hld.md, docs/system-design-lld.md,
docs/ai-logic-home-timetable.md, docs/ai-logic-myspace.md,
docs/myspace-indexing-pipeline.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md,
SECURITY.md, SUPPORT.md) which will break for other users; edit the links in
README.md to use relative paths (remove the /Users/... prefix) so they point to
the repository files (e.g., ./docs/system-design-hld.md or
docs/system-design-hld.md) ensuring all listed references resolve across
machines and CI.
🤖 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 8-13: Update the "Repository Architecture" section in README.md to
add direct links to the existing architecture and contribution docs by appending
a single line after the directory list that points to docs/system-design-hld.md
(HLD), docs/system-design-lld.md (LLD), and CONTRIBUTING.md; ensure the link
text matches the PR suggestion (e.g., "For detailed architecture and
contribution workflow, see [HLD](docs/system-design-hld.md),
[LLD](docs/system-design-lld.md), and [CONTRIBUTING.md](CONTRIBUTING.md)"), so
readers can quickly navigate from the described folders to the full HLD/LLD and
contribution guide.

---

Outside diff comments:
In `@README.md`:
- Around line 40-48: The README contains hardcoded absolute file paths for links
(e.g., docs/system-design-hld.md, docs/system-design-lld.md,
docs/ai-logic-home-timetable.md, docs/ai-logic-myspace.md,
docs/myspace-indexing-pipeline.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md,
SECURITY.md, SUPPORT.md) which will break for other users; edit the links in
README.md to use relative paths (remove the /Users/... prefix) so they point to
the repository files (e.g., ./docs/system-design-hld.md or
docs/system-design-hld.md) ensuring all listed references resolve across
machines and CI.
🪄 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: 9e7bf387-44d0-4708-b667-7bf12e5625e3

📥 Commits

Reviewing files that changed from the base of the PR and between 3cb6041 and af82be8.

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

Comment thread README.md
Comment on lines +8 to +13
## Repository Architecture

- `app/`: Expo React Native frontend for iPhone and Android
- `backend/`: Spring Boot API and timetable storage layer
- `ml-worker/`: Python OCR and timetable normalization worker
- `docs/`: System design documents and contribution guides
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 | 🟠 Major | ⚡ Quick win

Add links to HLD, LLD, and contribution guide.

The PR objectives explicitly require linking to existing architecture documentation. The current section describes directories but doesn't guide contributors to the detailed HLD, LLD, or CONTRIBUTING.md.

Consider adding a brief line after the directory list:

For detailed architecture and contribution workflow, see [HLD](docs/system-design-hld.md), [LLD](docs/system-design-lld.md), and [CONTRIBUTING.md](CONTRIBUTING.md).

This keeps the section scannable while fulfilling the requirement to "link to existing documentation rather than duplicate it."

🤖 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 8 - 13, Update the "Repository Architecture" section
in README.md to add direct links to the existing architecture and contribution
docs by appending a single line after the directory list that points to
docs/system-design-hld.md (HLD), docs/system-design-lld.md (LLD), and
CONTRIBUTING.md; ensure the link text matches the PR suggestion (e.g., "For
detailed architecture and contribution workflow, see
[HLD](docs/system-design-hld.md), [LLD](docs/system-design-lld.md), and
[CONTRIBUTING.md](CONTRIBUTING.md)"), so readers can quickly navigate from the
described folders to the full HLD/LLD and contribution guide.

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.

Add repository architecture map for new contributors

1 participant