Developing Openrig
Use when changing OpenRig's own source in a clone of the openrig repository: finding...
Install
npx skills add mvschwarz/openrig --skill developing-openrig -g -a claude-code -y- Repository
- mvschwarz/openrig8.5k
- Category
- Design
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 1,384 tokens
- Runs scripts
- No, instructions only
What it does
Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRig daemon your own session runs on, judging whether a diff touches a high-risk area, or preparing a pull request. Not for operating rigs (openrig-skills) or designing rig topologies.
Developing OpenRig
This skill is a map to the other maps. Each one is incomplete and may be stale: where a map and the code disagree, the code is right, and fixing the map is a welcome contribution.
First: which OpenRig are you in?
If you are an agent running inside OpenRig, two different OpenRigs are in play:
- The installed one runs your session.
rig --versionandrig daemon statusdescribe it. - The checkout is what you're changing.
git rev-parse HEADdescribes it.
Restarting the installed daemon does not run your checkout, and stopping it stops the agents running on it, including you. Test your change with the repo's own harnesses, which start a private daemon and tmux server (see "Test it" below), not by restarting the daemon you live in.
