docs: Update skill guidance for Round-7 pause-point, screenshot, and simulate-keyboard outcomes#1925
Conversation
…shot, and simulate-keyboard The Round-7 verification feedback showed agents losing time to guidance gaps rather than tool defects, so each note captures a contract the tools cannot express in their responses alone: - Rewrite the pause-point Quick Check Template around --trigger (added in round 7): one foreground command replaces the backgrounded-await dance, removing the arm-vs-input race the old template had to explain around. - Fast-Progressing Games: document the residual race when a command round-trip exceeds the game's own tick interval, and the rewrite-the-interval-field remedy that removes the race outright. - Reading CapturedVariables: physics-callback Rigidbody values can be mid-solver intermediates; a differing post-hoc read is not a capture bug. - Physics message methods: require fresh-contact evidence before treating HitCount=0 as the existing-instance miss (a stale pre-arm counter proves nothing), matching the retraction in PR #1922. - Screenshot: always use the response ImagePath; the output directory accumulates captures, so ls -t can pick a stale file. - simulate-keyboard: a pause landing during the Press duration wait now reports InterruptedByPausePoint=true with pause priority over a satisfied duration (PR #1919) - document it as a report, not a failure. Generated .claude/.agents copies regenerated via uloop skills install.
|
Warning Review limit reached
Next review available in: 5 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 (9)
✨ 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 |
The sentence prevents a wasteful follow-up await-pause-point call after a hit returned by enable-pause-point --await; the --trigger rewrite dropped it unintentionally.
1ed1e64
into
feature/round7-pause-point-improvements
Summary
Round-7 verification feedback (To-Do 13/14) showed agents losing time to guidance gaps rather than tool defects. This PR updates the source skill definitions and regenerates the
.claude//.agents/copies. Docs only — no code changes.--trigger(feat: Add --trigger to await-pause-point for one-command verification #1920). One foreground command arms, fires the input in-process after arm confirmation, and waits — replacing the backgrounded-await sequence and its arm-vs-input race caveats. Split-step fallback retained for non-single-command triggers.execute-dynamic-code.execute-dynamic-coderead is the solver finishing, not a capture bug.HitCount=0needs fresh-contact evidence (a stale pre-arm counter proves nothing) before it is treated as the miss.ImagePath; the output directory accumulates captures, sols -tcan silently pick a stale file.Pressduration wait returns promptly withInterruptedByPausePoint: true, with pause priority over a satisfied duration (fix: Detect pause-point interruption during Press/KeyDown observation wait #1919) — documented as the pause reporting in, not a delivery failure.Verification
dist/darwin-arm64/uloop skills install --claude --agentsregenerated;diffconfirms the tracked copies match the sources byte-for-byte.pause_point_trigger.gofor--triggerconstraints,PressLifetimeIterationResolver.ResolvePostWaitOutcomefor pause priority).Part of Round-7 (To-Do 13–14). Base:
feature/round7-pause-point-improvements.