feat: add resolve_css_api anti-hallucination tool#162
Conversation
Resolves every ::part(), CSS custom property, and slot reference against actual CEM data. Returns structured report with valid/invalid status and fuzzy-match suggestions for typos. 20 tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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
resolve_css_apiMCP tool that validates every::part(), CSS custom property, and slot reference against actual CEM dataAnti-hallucination impact
When agents call
resolve_css_apibefore finalizing CSS, they get immediate feedback on whether::part(content)actually exists onsl-dialog(it doesn't — the valid parts arebase,overlay,panel,header,body,footer, etc.)Test plan
🤖 Generated with Claude Code