jim60105/update-github-actions-version
skills/update-github-actions-version/SKILL.md
Update GitHub Actions versions in workflow files, focusing only on major version changes. Use when the user wants to update action versions, check for outdated GitHub Actions, or upgrade workflow dependencies to their latest major versions.
$ install --global
skillsauthnpx skillsauth add jim60105/copilot-prompt update-github-actions-versionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 26, 2026, 7:44 AM23.3s1 file scanned
SKILL.md
- name:
- update-github-actions-version
- description:
- Update GitHub Actions versions in workflow files, focusing only on major version changes. Use when the user wants to update action versions, check for outdated GitHub Actions, or upgrade workflow dependencies to their latest major versions.
- license:
- GFDL-1.3-or-later
- author:
- [email protected]
Update GitHub Actions Version
Update action versions in GitHub Actions workflow files, focusing on major version changes only.
Important Principles: Explanation of GitHub Actions Version Tagging System
- Using a major version number (e.g.,
v4) automatically fetches the latest minor and patch versions. - For example,
actions/checkout@v4will automatically get versions likev4.2.2,v4.3.0. - Do not update from
v4to a specific version likev4.2.2— this is unnecessary. - Only update when the major version changes (e.g., from
v5tov6).
Note: Skip
fatjyc/[email protected]updates as the new version is broken.
Steps
0. Find Workflow Files
Look for files in .github/workflows/ recursively. Note that composite actions may be used — read both the composite action and the calling workflow simultaneously.
1. Check Current Versions
Analyze the action versions used in the workflow files.
2. Query Latest Versions
Query each action's latest version:
https://github.com/{owner}/{repo}/releases/latest
3. Identify Actions Needing Updates
Only update actions where the major version has changed:
- ✅ Update:
docker/build-push-action@v5→@v6 - ❌ Skip:
actions/checkout@v4→@v4.2.2
Note: Skip
fatjyc/[email protected]updates as the new version is broken and v6.0 is fine.
4. Obtain Changelogs
For actions requiring updates, retrieve changelogs to understand breaking changes.
5. Update Files
Update version numbers and make adjustments for any breaking changes.
6. Commit Changes
Git add and commit your changes with a clear message indicating the updates made.
Example Illustration
✅ Correct Update
# From
uses: docker/build-push-action@v5
# Update to
uses: docker/build-push-action@v6
❌ Incorrect Update (Unnecessary)
# From
uses: actions/checkout@v4
# Incorrectly updated to
uses: actions/checkout@v4 .2 .2
✅ Correct Practice (Keep Unchanged)
# Keep unchanged
uses :actions / checkout @ v 4
GitHub will automatically use the latest v 4.x.x release
Related Skills
jim60105/documentation-writer
development
VerifiedTrustedCommunity
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
19SKILL.mdUpdated May 29, 2026
jim60105/doc-coauthoring
testing
VerifiedTrustedCommunity
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
19SKILL.mdUpdated May 29, 2026
jim60105/docsify
tools
VerifiedTrustedCommunity
Comprehensive guide for building, configuring, customizing, and deploying Docsify documentation sites. Use when the user wants to (1) initialize a new Docsify site, (2) add or organize Markdown pages, sidebars, navbars, or cover pages, (3) configure `window.$docsify` options, (4) customize themes / CSS variables / fonts, (5) install built-in or third-party Docsify plugins (search, GA, emoji, zoom, copy-code, comments, pagination, tabs, etc.), (6) write a custom Docsify plugin using lifecycle hooks, (7) use Docsify Markdown helpers (callouts, link attributes, image attributes, heading IDs, task lists, embed files with `:include`), (8) deploy to GitHub Pages, GitLab Pages, Netlify, Vercel, Firebase, Docker, Nginx, etc., (9) enable PWA / offline mode, virtual routes, or Vue compatibility, or (10) upgrade a Docsify site from v4 to v5. Triggers on mentions of "docsify", "_sidebar.md", "_navbar.md", "_coverpage.md", "$docsify", or `docsify-cli`.
19SKILL.mdUpdated May 28, 2026
jim60105/chinese-content-writing-guideline
testing
VerifiedTrustedCommunity
Writing guidelines for producing high-quality Traditional Chinese (zh-TW) content. Use when writing any kind of content. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing Chinese content for tone, style, and terminology compliance.
19SKILL.mdUpdated Apr 6, 2026