agentsclimarketplace
Sign in

Github actions updater

Skill lynicis/actup/skills/github-actions-updater

Helps users keep GitHub Actions workflow files up to date. Use when the user mentions GitHub Actions, workflow files, upgrading actions, bumping action versions, CI/CD maintenance, or deprecated actions.From its SKILL.md

Install
npx -y skills add lynicis/actup --skill github-actions-updater

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 1 command, including `gh api repos/{owner}/{repo}/tags --jq '.[].name'`.
  • fetches URLsInstructs the agent to fetch 1 URL, including https://api.github.com/repos/{owner}/{repo}/tags.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.3 KB, 791 tokens by cl100k_base, as published. Nobody here has run it

GitHub Actions Updater

Keep .github/workflows/*.yml and .github/workflows/*.yaml files current by scanning actions, resolving latest versions, and suggesting upgrades.

Quick start

When the user asks something like:

"Update my GitHub Actions" "Which actions are out of date?" "Bump actions in my workflows"

Follow the workflow below and return a Markdown report with diff-style suggestions.

Workflow

  1. Scan workflows

    • Find all .github/workflows/*.yml and .github/workflows/*.yaml files.
    • If none exist, tell the user and stop.

  2. Extract uses: refs

    • Parse each workflow for uses: lines.
    • Skip:
      • Local paths: ./...
      • Docker refs: docker://...
      • Full SHA commits: anything that looks like a 40-char hex SHA
    • Record: action, current_version, workflow_file, line_number.

  3. Resolve latest version

    • Split each action into owner/repo.
    • Try tools in this order:
      1. gh api repos/{owner}/{repo}/tags --jq '.[].name' if gh is available.
      2. fetch on https://api.github.com/repos/{owner}/{repo}/tags.
      3. Brave Search / Google Search MCP for "{owner}/{repo} latest release tag".
    • Filter tags to valid semver.
    • Prefer major tags (v5) over full semver (v5.3.1) by default.
    • If no major tag exists, fall back to the highest semver tag.

  4. Detect breaking changes

    • If the latest version is a higher major than the current version, mark it as a breaking change.
    • Cross-check the embedded registry below for known warnings.

  5. Generate suggestion report

    • Produce a Markdown report with:
      • Summary table: action | current | latest | breaking? | file
      • Diff blocks per action
      • Breaking-change warnings with ⚠
    • Do not edit workflow files unless the user explicitly asks.

Breaking-change registry

- action: actions/checkout
  from_major: 3
  to_major: 4
  warning: "Node runtime upgraded from 16 to 20. Check custom runners and self-hosted setup."
- action: actions/setup-node
  from_major: 3
  to_major: 4
  warning: "Node 16 runtime deprecated; Node 20 is now used."
- action: actions/setup-go
  from_major: 4
  to_major: 5
  warning: "Node 20 runtime. Verify any custom cache keys or side effects."

Output template

## GitHub Actions update report

| Action | Current | Latest | Breaking? | File |
|--------|---------|--------|-----------|------|
| actions/checkout | v3 | v4 | ⚠ yes | .github/workflows/ci.yml |

### Suggested changes

`.github/workflows/ci.yml`:
```diff
- uses: actions/checkout@v3
+ uses: actions/checkout@v4

Breaking-change warnings

  • actions/checkout@v3 → v4: Node runtime upgraded from 16 to 20. Check custom runners and self-hosted setup.

## Rules

- Never silently write workflow files.
- Always show a diff-style preview before any edit.
- If GitHub API rate limits are hit, fall back to search MCPs or manual guidance.
- If an action has no semver tags, note it as "unable to determine latest version".

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.