Skip to content

docs: note editor-context Screen values and captured-variable filtering in skills - #2315

Merged
hatayama merged 2 commits into
v3-betafrom
docs/skill-screen-and-captured-variable-filter
Aug 20, 2026
Merged

hatayama merged 2 commits into
v3-betafrom
docs/skill-screen-and-captured-variable-filter

Conversation

@hatayama

@hatayama hatayama commented Aug 20, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • execute-dynamic-code now states that Screen.width/Screen.height in this tool are Editor pixels, not Game View resolution, and points to ViewportPointToRay for a Game View center ray.
  • pause-point now points from --captured-variables to --captured-variable-names when the default full dump is noisy.

User Impact

  • Before: a Game View raycast written with Screen.* missed, and agents spent extra round trips assuming the raycast was broken.
  • After: the skill states the Editor-context contract up front.
  • Before: --captured-variables full buried the locals of interest under unrelated InstanceField values, and --captured-variable-names was not discoverable from that flag's description.
  • After: the --captured-variables bullet itself points at the name filter.

Changes

  • Two sentences under execute-dynamic-code Code Rules.
  • One bullet under pause-point Reading CapturedVariables.
  • Regenerated .claude/ and .agents/ skill copies. Parameter tables are unchanged, so default-tools.json stayed up to date.

Verification

  • scripts/sync-tool-docs.sh → cli/common/tools/default-tools.json is already up to date.
  • dist/darwin-arm64/uloop skills install --claude --agents → Updated: 2, Skipped: 18

Review in cubic

…ng in skills

execute-dynamic-code snippets see Editor Screen pixels, not Game View resolution.
pause-point --captured-variables now points at --captured-variable-names when the full dump is noisy.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Aug 20, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 579a80b2-1823-4d46-9197-e13adb31b563

📥 Commits

Reviewing files that changed from the base of the PR and between 8929385 and 71b339d.

📒 Files selected for processing (3)
  • .agents/skills/uloop-pause-point/SKILL.md
  • .claude/skills/uloop-pause-point/SKILL.md
  • Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/SKILL.md

Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The PR updates six skill documents. Execute-dynamic-code guidance covers Editor pixels and Game View-center rays. Pause-point guidance covers full variable capture, truncation limits, and output filtering.

Changes

Skill documentation

Layer / File(s) Summary
Game View ray guidance
.agents/skills/uloop-execute-dynamic-code/SKILL.md, .claude/skills/uloop-execute-dynamic-code/SKILL.md, Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/Skill/SKILL.md
The documentation distinguishes Editor pixels from Game View resolution and documents ViewportPointToRay for the Game View center.
Pause-point capture guidance
.agents/skills/uloop-pause-point/SKILL.md, .claude/skills/uloop-pause-point/SKILL.md, Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/SKILL.md
The documentation explains retained values, truncation limits, and filtering with --captured-variable-names or --captured-variables names.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to 71b33

This documentation-only change clarifies editor-context screen values and captured-variable filtering; no actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description check ✅ Passed The description directly explains the documentation updates, user impact, regenerated copies, and verification steps.
Title check ✅ Passed The title clearly summarizes the documentation changes for Editor-context Screen values and captured-variable filtering.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/skill-screen-and-captured-variable-filter

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.

full keeps each captured entry's Value; it does not change which variables were captured, and capture caps still apply.

Co-authored-by: Cursor <cursoragent@cursor.com>
@hatayama
hatayama merged commit 21678e9 into v3-beta Aug 20, 2026
8 checks passed
@hatayama
hatayama deleted the docs/skill-screen-and-captured-variable-filter branch August 20, 2026 18:29
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