fix: Correct skill descriptions and use error-prone command examples - #2012
Conversation
Round12 E2E verification showed agents copy the first example they read and extrapolate option values from description wording, so descriptions and examples must only show values that actually exist: - Align the simulate-keyboard / simulate-mouse-input / control-play-mode skill descriptions with real option values (no more "holds" without Press --duration, "held button input", or verbs that are not actions) - Switch the Fast-Progressing Games --trigger examples to --key Digit3 and state the Digit0-9/Numpad0-9 rule next to every keyboard example, because bare digits were silently parsed as enum ordinals - Correct the --trigger "no race" claim: the marker can hit before the trigger runs, and tell readers to load the triggered tool's skill first - Document frame-completed capture semantics with a Destroy example, physical-input hygiene during mouse verification, the scope of CapturedVariablesTruncated, and --max-preview-elements carrying into pause-point-status Generated skill copies under .claude/ and .agents/ are regenerated with "uloop skills install --claude --agents".
|
Warning Review limit reached
Next review available in: 28 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 Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThe PR synchronizes duplicated skill documentation, clarifying Play Mode actions, keyboard hold syntax, mouse-input verification, pause-point trigger behavior, captured-variable semantics, and digit-key examples. ChangesSkill documentation alignment
Estimated code review effort: 1 (Trivial) | ~5 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 |
The control-play-mode description omitted the Resume alias and the simulate-keyboard description implied Press --duration is the only way to hold a key, contradicting the skill body which also documents open-ended KeyDown/KeyUp holds. Align both descriptions with the documented action sets and regenerate the skill copies.
1b99b98
into
feature/cli-discoverability-integration
Summary
PR-1 of the round12 CLI-discoverability plan. Skill documents only — no code changes.
Round12 E2E verification (3 agents) showed that agents copy the first example they read and extrapolate option values from description wording. This PR makes descriptions and examples show only values that actually exist, and puts load-bearing facts inline where they are read.
Changes
simulate-keyboard,simulate-mouse-input,control-play-mode):holds→holds (via Press --duration),held button input→long-press (LongPress),movement delta→movement delta (MoveDelta/SmoothDelta), and play-mode verbs → the actualPlay/Stop/Pause/Step/Statusvalues.--triggerexamples use an error-prone key (--key Digit3instead ofSpace) in the Fast-Progressing Games section of the pause-point skill and its reference, with the digit rule stated right after every keyboard example:Digit keys are `Digit0`-`Digit9` or `Numpad0`-`Numpad9` — bare `0`-`9` is rejected.The Quick Check Template keepsSpacebut gains the same fact line (verification showed the template is what gets copied).--triggerrace claim corrected: the marker can hit before the trigger executes (every-frame lines); the trigger is then preflight-rejected and runs nothing. One imperative added: load the triggered tool's skill before writing a non-example trigger command.Destroy(obj)example for frame-completed live references,CapturedVariablesTruncatedbeing unrelated to the name filter, and--max-preview-elementsat enable time carrying into laterpause-point-statusresponses..claude/and.agents/regenerated viauloop skills install --claude --agents.Verification
uloop simulate-keyboard --action Press --key Digit3executed against the running Editor in PlayMode:Success: true(the new example works as written).holdsoutsideholds (via Press --duration), noheld button input, nostart,in the three frontmatter descriptions.skills installdiff contains only the files touched by this PR.