Repository navigation
Lint and test runner tools with auto-detection - #10
Conversation
Auto-detect project lint/test commands, structured diagnostic parsing, and optional auto-run-after-edit for self-correcting feedback loops.
Auto-detect lint/test commands from project config files: - package.json scripts, eslint, tsconfig (JS/TS) - pyproject.toml, ruff, pytest (Python) - Cargo.toml, clippy (Rust) - go.mod, golangci-lint (Go) - Gemfile, rubocop (Ruby) - Makefile targets Structured diagnostic parsing for file:line:message output.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 4 minutes and 22 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
linttool: auto-detect and run project linter, return structured diagnosticsrun_teststool: auto-detect and run project tests, return structured resultsprojectDetector.ts: scans for package.json, pyproject.toml, Cargo.toml, go.mod, Gemfile, MakefileoutputParsers.ts: parse TypeScript, generic file:line:col formatsTest plan