From rwx
Review an RWX config generated from a GitHub Actions migration. Compares the source workflow against the generated config to catch semantic gaps, missing steps, and optimization opportunities. TRIGGER when: the user asks to review, validate, or check an RWX config that was migrated from GitHub Actions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rwx:review-gha-migrationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fetch and read the cheat sheet before starting. Do NOT use WebFetch — it
Fetch and read the cheat sheet before starting. Do NOT use WebFetch — it
summarizes and drops critical details. Instead, use Bash to run rwx docs pull
and read stdout directly:
rwx docs pull /docs/rwx/migrating/gha-cheat-sheet
You are reviewing an RWX config that was generated from a GitHub Actions workflow migration. Your job is to catch problems the implementer missed. Approach this as a skeptical reviewer, not as someone defending prior work.
The user provides the RWX config path as $ARGUMENTS. If no path is provided,
list the files in .rwx/ and ask the user which config to review.
Then locate the corresponding source GitHub Actions workflow. Look for clues:
.rwx/ci.yml likely came from
.github/workflows/ci.yml)Read both files in full.
Build a checklist from the GitHub Actions workflow. For each item, you will verify it was correctly translated. Extract:
needs: dependenciesif: expressions)Go through your checklist item by item and verify each one is accounted for in the RWX config. For each item, classify it as:
Pay special attention to:
if: conditionals that were lost or simplified incorrectlyIf you don't already have the reference documentation in context, fetch it now.
Do NOT use WebFetch — it summarizes and drops critical details. Instead, use
Bash to run rwx docs pull for each doc and read stdout directly. Run both in a
single turn as parallel Bash calls:
rwx docs pull /docs/rwx/migrating/rwx-reference — full RWX config syntaxrwx docs pull /docs/rwx/migrating/gha-reference — GHA-to-RWX concept mappingIf 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.
Using the reference documentation, check whether the config takes full advantage of RWX capabilities:
run: steps installing tools that have
RWX package equivalents?npm ci followed by npm run build) — these should be separate tasks
for independent cacheability.Check the RWX config for structural issues:
use referencesrwx lint .rwx/<name>.yml and review the diagnosticsOutput a structured review with these sections:
Summary: One-line verdict — is this migration correct and ready, or does it need changes?
Issues (if any): A numbered list of problems found, each with:
blocking (must fix before using) or suggestion (improvement
opportunity)Checklist: A markdown checklist showing each source workflow item and whether it was correctly translated:
- [x] Job: build — correctly translated as task `build`
- [ ] Job: deploy — missing, no TODO comment
- [x] Trigger: push to main — correctly mapped
- [ ] Secret: DEPLOY_KEY — referenced but not in secrets mapping
Optimization opportunities: Any RWX-specific improvements not yet applied.
If you find blocking issues, offer to fix them directly.
npx claudepluginhub rwx-cloud/skills --plugin rwxValidates, lints, audits, and fixes GitHub Actions workflows using actionlint and act. Includes local testing, error fixes, and public action version checks.
Checks and configures GitHub Actions CI/CD workflows for container builds, tests, and releases. Updates action versions, adds caching, multi-platform builds, and audits missing workflows.
Creates, audits, and optimizes GitHub Actions workflows for CI/CD, matrix builds, reusable workflows, composite actions, caching, and security hardening like pinning and permissions.