docs: Document the resolved-camera fields in the raycast skill#1905
Conversation
PR #1904 added CameraName/CameraPath to raycast responses so an agent can tell which camera Camera.main resolved to. Without a skill note, agents have no reason to look at these fields when a "No physics hit" result looks wrong — the Round-5 dogfooding case was exactly a stray MainCamera-tagged camera silently winning the resolution. Document the fields in the Output list and point to them as the first check. Generated .claude/ and .agents/ copies regenerated via 'uloop skills install --claude --agents'.
|
Warning Review limit reached
Next review available in: 48 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 reviews. How do review 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 refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ 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 |
b289ceb
into
feature/pause-point-round5-integration
Summary
Follow-up to PR #1904 (resolved-camera fields in raycast responses). Docs only.
Packages/src/Editor/FirstPartyTools/Raycast/Skill/SKILL.md: documentCameraName/CameraPathin the Output list, and tell agents to check them first when aNo physics hitresult looks wrong (a strayMainCamera-tagged camera can silently win theCamera.mainresolution — the exact Round-5 dogfooding failure)..claude/and.agents/copies viauloop skills install --claude --agents; verified the generated diff matches the source.Verification