chore: add .coderabbit.yaml configuration for CodeRabbit AI reviews

[Vaishnavi10706]

Fixes: #18

Summary

This PR adds a .coderabbit.yaml file to configure CodeRabbit AI reviews for the repository.

Changes Introduced

The configuration:

Enables automatic pull request reviews

Provides high-level summaries of changes

Displays review status checks

Ignores build and dependency directories such as node_modules, dist, and build

Impact

Improves automated code review workflow

Enhances visibility into PR changes

Ensures irrelevant generated files are excluded from AI review

Please review and let me know if any modifications or improvements are required. I’ll be happy to update it accordingly.

Summary by CodeRabbit

• Chores
  • Added configuration for automated code review workflows and quality assurance tooling to enforce best practices and security standards across the codebase, including support for multiple code quality tools and linting frameworks.

[kpj2006]

try to follow template repo coderabbit.yaml

[Vaishnavi10706]

Hi @kpj2006,

Thank you for the feedback. I’ll update the .coderabbit.yaml to fully align with the Template Repo configuration and ensure consistency across the organization.

I’ll push the updated version shortly.

Thank you for the guidance!

[coderabbitai]

📝 Walkthrough

Walkthrough

A new CodeRabbit configuration file is introduced that defines language settings, enables automated review tools (eslint, markdownlint, yamllint, gitleaks, github-checks), configures review automation profiles, and specifies path-based review instructions for JavaScript, HTML, CSS, and Markdown files.

Changes

Cohort / File(s)	Summary
CodeRabbit Configuration .coderabbit.yaml	Initial configuration file defining language settings, early access flags, chat auto-reply behavior, review automation workflows (high_level_summary, review_status, changed_files_summary, request_changes_workflow), enabled tooling suite, pre-merge checks, and path-specific review instructions for code quality, accessibility, performance, security, and documentation standards.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A config file hops into the warren,
With linters and rules to keep code from errin',
Path-based reviews, workflows so neat,
CodeRabbit's toolbox now complete! 🛠️

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately describes the main change: introducing a .coderabbit.yaml configuration file for CodeRabbit AI reviews.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 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: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.coderabbit.yaml:
- Around line 17-18: The config includes a redundant base_branches entry listing
"main"; remove the base_branches key (and its list containing "main") from the
.coderabbit.yaml so only non-default branches are specified when needed, leaving
the default branch behavior unchanged; if you intended to target other branches,
replace the list with those branch names instead of "main".
- Around line 50-55: The YAML uses an unsupported field 'instructions' under
'reviews'; remove that key and instead create a 'path_instructions' entry under
the same 'reviews' section containing the existing bullet list, scoped to a
catch-all glob (e.g., "**/*") so the content is recognized by the CodeRabbit
schema; update the 'reviews' mapping to replace 'instructions' with
'path_instructions' and move the four/five bullet items into that new field.