fix(package): Update stale pause point guidance in tool skills#1688
Merged
Conversation
The source pause point rework (enable-pause-point --file/--line with CapturedVariables) left four tool skills describing the retired workflow: - execute-dynamic-code told agents to add a Debug.Log before UloopPausePoint.Pause() and read it back via get-logs. CapturedVariables replaced that flow, and skills must not surface the emergency-only handwritten-marker API. - simulate-keyboard and simulate-mouse-input documented PausePointId as coming from UloopPausePoint.Pause() instead of the derived <file>:<line> id returned by enable-pause-point. - simulate-mouse-ui never documented the InterruptedByPausePoint, PausePointId, PausePointHitCount, and PausePointHits response fields or the Message dispatch-state contract added with the mid-command interruption fix. - The shared "place markers ... not immediately after" wording contradicted the pause point skill's Line Placement guidance that mid-command pauses are safe and return promptly. Generated .claude/.agents copies are regenerated and byte-identical to the sources.
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (12)
📝 WalkthroughWalkthroughDocumentation for dynamic-code inspection and keyboard/mouse simulation now reflects source pause points, ChangesPause-point guidance
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Merged
This was referenced Jul 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
enable-pause-point --file/--line+CapturedVariables) shipped in feat: Enable pause points by source file and line #1684 / fix(package): Stop tools from hanging when a pause point fires mid-command #1685UloopPausePoint.Pause), which must only be surfaced through patch-failure hintsChanges
UloopPausePoint.Pause()and read it back via get-logs" workflow for method locals is replaced with enabling a source pause point and readingCapturedVariablesfrom the hit response (no code edit or recompile)PausePointId/PausePointHitCountoutput docs now describe the derived<file>:<line>id returned byenable-pause-pointinstead ofUloopPausePoint.Pause()InterruptedByPausePoint/PausePointId/PausePointHitCount/PausePointHitsresponse fields added in fix(package): Stop tools from hanging when a pause point fires mid-command #1685 (keyboard and mouse-input already documented them) and theMessagedispatch-state contract (whether the pointer event fired before the pause)simulate-*" is replaced with the Line Placement guidance that mid-command pauses are safe and return promptly; "remove temporary pause-point/log instrumentation" becomes "clear pause points".claude/and.agents/copies regenerated viauloop skills install --claude --agents, byte-identical to sourcesTest plan
cmpconfirms all copies byte-identical to sourcesgrepconfirms zeroUloopPausePointmentions remain across all skill sources