Repository navigation
docs(skills): draw the line between the rigs and openrig-skills descr… - #1174
Conversation
…iptions Both descriptions claimed getting a rig back, a watchdog wake and an OpenRig upgrade, and neither named the other, so the wording of the request decided which skill loaded. The line is now who is asking: rigs is a person in their own session (install, set up, start, update, re-attach, share, join); openrig-skills is an agent already inside a rig (fleet recovery, seat handover, watchdog wakes, in-rig upgrades). Each description names the other in one clause. The package copy of rigs, the plugin and canonical copies of openrig-skills, and the edge digests follow the source edits.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The descriptions consistently distinguish person-session setup and recovery from in-rig operations, and their generated digests match. No actionable merge risk remains. Pre-merge checks |
 |
| Check name | Status | Explanation |
|---|---|---|
| Description Check |  |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | |
The title clearly and concisely describes the main change: distinguishing the roles of the rigs and openrig-skills descriptions. |
| Linked Issues check | |
Issue [#1171] requires a boundary between rigs user-session requests and openrig-skills in-rig requests. The changed descriptions define that boundary. rigs covers setup, start, update, re-attac… |
| Out of Scope Changes check | |
The reviewed changes update only the two skill descriptions and their synchronized package, plugin, and canonical copies. These changes directly support [#1171]. The reported generated digest update s… |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
✨ Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 @coderabbitai help to get the list of available commands.
|
Thanks, @ehnruiz, for following up on #1171 with this. As you describe it, the line is drawn by who's asking (a person in their own Claude Code or Codex session for rigs, an agent already running inside a rig for openrig-skills), and only the two description lines change, with the copies regenerated. We'll review it and follow up here. |
|
Thanks, @ehnruiz, for turning #1171 into a PR so quickly. Drawing the line by who's asking works well: One change in
A minimal wording that does both (adjust as you see fit):
Optionally, Then regenerate the copies and the digest as before. |
…d person in openrig-skills rigs keeps the person's own words, "getting back to" their agents, next to re-attaching, and says it covers bringing a stopped team back from their own session, so recovery is on both sides as the pull request claims. openrig-skills follows the third-person convention and its pointer back to rigs uses the same words. Copies and the edge digests regenerated.
Done in 772425a. rigs now keeps "getting back to" next to re-attaching and says it includes bringing a stopped team back, using your wording. openrig-skills is in the third person, and its pointer back to rigs names the same cases so recovery reads the same from both sides. Copies and the digest regenerated; npm run test:repo passes. |
openrig-review
left a comment
openrig-review
left a comment
There was a problem hiding this comment.
Approved at 772425a. The rigs and openrig-skills descriptions now divide by who is asking: rigs for a person in their own Claude Code or Codex session (install, start, update, getting back to their agents, bringing a stopped team back), openrig-skills for an agent already running inside a rig. Each names the other in one clause. The generated copies and skill-edge digests match their sources byte for byte. Required CI passed at this head, on a base that already includes main's only later change to these files.
— dev60-planner@v-openrig-build
Thanks @mvschwarz looking forward to making more contributions! |
3 participants
Closes #1171.
Both descriptions claimed getting a rig back, a watchdog wake and an OpenRig upgrade, and neither named the other, so the wording of the request decided which skill loaded.
The line is drawn by who is asking rather than by topic:
rigs is a person in their own Claude Code or Codex session: install, set up, start, update, re-attach, share a team, join one.
openrig-skills is an agent already running inside a rig: fleet recovery, seat handover, watchdog wakes, in-rig upgrades, and the rest of the index.
Each description now names the other in one clause. Recovery and upgrades stay on both sides on purpose, because "my rig is down" and "upgrade OpenRig" mean different things from each vantage; that is the part of the line most open to moving.
Only the two description lines change. The package copy of rigs, the plugin and _canonical copies of openrig-skills, and scripts/skill-edge-digests.generated.json follow the source edits (node scripts/regen-edge-digests.mjs). npm run test:repo passes, including mirror-skills --check.
Observed on 0.6.8 (aa126c7); the descriptions are unchanged on main at v0.6.9.
Summary by CodeRabbit