Skip to content

docs: Document the resolved-camera fields in the raycast skill#1905

Merged
hatayama merged 1 commit into
feature/pause-point-round5-integrationfrom
docs/raycast-resolved-camera-skill
Jul 21, 2026
Merged

docs: Document the resolved-camera fields in the raycast skill#1905
hatayama merged 1 commit into
feature/pause-point-round5-integrationfrom
docs/raycast-resolved-camera-skill

Conversation

@hatayama

@hatayama hatayama commented Jul 21, 2026

Copy link
Copy Markdown
Owner

Summary

Follow-up to PR #1904 (resolved-camera fields in raycast responses). Docs only.

  • Packages/src/Editor/FirstPartyTools/Raycast/Skill/SKILL.md: document CameraName / CameraPath in the Output list, and tell agents to check them first when a No physics hit result looks wrong (a stray MainCamera-tagged camera can silently win the Camera.main resolution — the exact Round-5 dogfooding failure).
  • Regenerated .claude/ and .agents/ copies via uloop skills install --claude --agents; verified the generated diff matches the source.

Verification

  • Docs-only change; source SKILL.md and generated copies are byte-consistent.

Review in cubic

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'.
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1d5d3aa0-2e17-47bc-aa24-98ded7916a1f

📥 Commits

Reviewing files that changed from the base of the PR and between 2b68047 and b1150b8.

📒 Files selected for processing (3)
  • .agents/skills/uloop-raycast/SKILL.md
  • .claude/skills/uloop-raycast/SKILL.md
  • Packages/src/Editor/FirstPartyTools/Raycast/Skill/SKILL.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/raycast-resolved-camera-skill

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

Comment @coderabbitai help to get the list of available commands.

@hatayama
hatayama merged commit b289ceb into feature/pause-point-round5-integration Jul 21, 2026
1 of 2 checks passed
@hatayama
hatayama deleted the docs/raycast-resolved-camera-skill branch July 21, 2026 03:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant