Development

[anujmindfire]

Pull Request Title

Provide a brief title that describes your changes (e.g., "Add feature X" or "Fix issue #123").

---

Description

What does this PR do?

Provide a concise summary of your changes and what issue or feature they address.

Related Issues

Link any related issue(s) with references to help reviewers understand the context.

• Closes #ISSUE_NUMBER (if applicable)

Type of Change

• 🐛 Bug fix
• 🚀 New feature
• 📄 Documentation update
• ⚙️ Code refactoring
• 🔧 Configuration or CI/CD change
• 🧹 Maintenance or dependency update

Checklist

Please ensure the following have been completed before submitting:

• I have formatted my code using gofumpt.
• I have managed imports using goimports or gci.
• I have run linter using golangci-lint.
• I have run tests using go test ./....
• I have updated the documentation as needed.
• I have added or updated tests for the changes in this PR.

Screenshots (if applicable)

Provide screenshots or GIFs if this PR changes the UI or has visible results.

Additional Context

Include any other context, references, or information that may be useful for the reviewers.

---

Thank you for your contribution!

We appreciate your efforts in making this project better.

[coderabbitai]

Warning

Review limit reached

@anujmindfire, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 58 minutes and 49 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5885488d-58e2-4a27-85c7-34c2d2dc0f7c

📥 Commits

Reviewing files that changed from the base of the PR and between d11456a and 0e6f67e.

📒 Files selected for processing (13)

• .github/workflows/ci.yml
• .github/workflows/release-docs.yml
• .github/workflows/release.yml
• .gitignore
• CONTRIBUTING.md
• README.md
• apps/cli/main.go
• apps/cli/tests/crawler_test.go
• apps/cli/tests/storage_test.go
• apps/docs/docs/features.mdx
• apps/docs/docs/installation.mdx
• apps/docs/docs/usage.mdx
• scan-results-quotes.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch development

---

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.}