Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →github/github-actions-runtime-upgrade-conventions
Upgrade GitHub Actions to supported runtimes by selecting safe action versions, preserving workflow behavior, and validating post-upgrade execution.
Passed 23 of 23 test cases with the skill, and 12 of 23 without it.
and 11 more in the full report
11 fixed12 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We noticed `actions/setup-go@v2` triggering runtime deprecation notes in our workflow run logs for `.github/workflows/go.yml`. Provide the corrected step definition line.
| Checked | Without skill | With skill |
|---|---|---|
| The actions/setup-go action uses a full commit SHA reference rather than a tag like @v4. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when editing GitHub Actions workflows to address deprecation warnings about action runtimes (for example Node.js runtime migrations).
.github/workflows/*.yml or .github/workflows/*.yaml.uses:.@v4 or @main) in final recommendations.Prioritize runtime review for these groups when warnings appear:
actions/*actions/setup-* (for example setup-node, setup-python, setup-dotnet)steps:
- uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608 # v4.3.1
- uses: actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8 # v4.0.4
When recommending upgrades, identify the latest compatible release first, then use the corresponding commit SHA with an optional version comment.
After changing action versions:
test cases passed, vs 12 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.