Stats
Actions
Tags
From rwx
Can be used to kick off local "run loops" on the RWX CI platform, or when understanding, creating or modifying an RWX CI/CD config or any other file in a .rwx directory. TRIGGER when: the user asks about RWX, wants to create or modify an RWX config, debug test failures, check a run status, or start a run loop.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rwx:rwxThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Ensure the user is signed in and on the latest version of the RWX CLI before
Ensure the user is signed in and on the latest version of the RWX CLI before
getting started: rwx whoami
Then, fetch the reference docs index with:
rwx docs pull /docs/rwx/migrating/rwx-reference
If you encounter a question not covered by these references, use
rwx docs search "<query>" to find the relevant documentation page, then
rwx docs pull the result.
If the user chooses, you can kick off an actual run on RWX:
rwx run .rwx/<name>.yml --wait
When the run finishes, results will be shown, and you can iterate in that fashion until the run passes.
No git push is required to invoke a run from the RWX CLI.
If you have been asked to check on run failures or CI failures, or if you have been asked to check the current run status of the current branch or a given branch:
rwx results -h
You may have been tasked with creating, modifying, or understanding/explaining an RWX CI/CD config for this project. Use the same aforementioned documentation.
When making changes, you can run validation on the config:
rwx lint .rwx/<name>.yml
npx claudepluginhub rwx-cloud/skills --plugin rwxMonitors Nx Cloud CI pipelines and handles self-healing fixes. Integrates with Nx Cloud for CI monitoring beyond native CI tools.
Runs commands, inspects repo state, debugs CI/builds, and makes narrow verified fixes with exact proof of what was executed and confirmed.