Added CONTRIBUTING.md file

[ananya-09]

Fixed the prerequisite and project structure links in table of content.
And corrected few minor errors on line 151.

Summary by CodeRabbit

• Documentation
  • Added a comprehensive contribution guide covering tech stack, prerequisites, step-by-step setup and installation, environment configuration for AI and database providers, how to run the app, and project structure navigation.
  • Included contribution guidelines, support contact, and best practices to help new contributors get started.

[vercel]

@ananya-09 is attempting to deploy a commit to the byteom's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

Adds a new CONTRIBUTING.MD file outlining contribution guidelines, tech stack, prerequisites, installation and setup steps (including environment variables), project structure, and support contact for InterviewAce.

Changes

Cohort / File(s)	Summary of Changes
Docs CONTRIBUTING.MD	Added comprehensive contribution guide covering tech stack, prerequisites, installation and setup steps, environment configuration (.env keys for Supabase and AI providers), development run instructions, project structure, and support contact.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

gssoc2025, gssoc, gssoc25, level1

Poem

A nibble, a note, a hop through the page,
New paths for contributors—step on the stage!
Env keys in pockets, scripts all set steady,
Docs like a burrow: welcoming and ready.
With paws on the keyboard, I thump with delight—let's ship by carrot-light! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Title Check	✅ Passed	The pull request title clearly and concisely describes the primary change, which is the addition of the CONTRIBUTING.md file, without extraneous detail or vague terminology. It directly references the main change in the changeset and would be understandable to team members reviewing PR history. The phrasing is brief yet specific, meeting the criteria for an effective title.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

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 47c0377 and aa19b31.

📒 Files selected for processing (1)

• CONTRIBUTING.MD (1 hunks)

[coderabbitai]

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 aa19b31 and 3521e79.

📒 Files selected for processing (1)

• CONTRIBUTING.MD (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

CONTRIBUTING.MD

16-16: Link fragments should be valid

(MD051, link-fragments)

---

19-19: Link fragments should be valid

(MD051, link-fragments)

[ananya-09]

Hello @byteom sir,
Please add labels of GSSOC'25 and the task level in this PR so that it can be counted a successful pr.

[ananya-09]

@byteom Sir my PR isn't showing that it is merged, please review and merge it if its appropriate to do so, So that it can be counted as a successful contribution. This pr is not yet counted in my contributions.