update-github-action

Resolve GitHub Actions tags to immutable commit SHAs for workflow steps.

3|2|Updated May 20, 2026
One-click install
npx skills add https://github.com/openkaiden/openshell-image-builder --skill update-github-action
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-github-action
Source: https://github.com/openkaiden/openshell-image-builder/tree/main/.agents/skills/update-github-action
Command: npx skills add https://github.com/openkaiden/openshell-image-builder --skill update-github-action

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the security risk of using mutable GitHub Action tags by automatically pinning them to specific, immutable commit SHAs.

Core Features & Use Cases

  • SHA Pinning: Fetches the latest commit SHA for any GitHub Action to ensure workflow stability and security.
  • Version Tracking: Maintains a consistent version comment format for auditability and Dependabot compatibility.
  • Use Case: When adding a new workflow step or updating an existing one, use this Skill to retrieve the correct SHA and format the uses line to prevent silent dependency changes.

Quick Start

Use the update-github-action skill to pin the actions/checkout action to its latest commit SHA.

Frequently Asked Questions about update-github-action

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pin GitHub Actions to immutable commit SHAs?

To pin GitHub Actions to immutable commit SHAs, this Skill resolves mutable action tags by querying repository release metadata via the GitHub CLI and updates workflow steps with the specific commit SHA. It maintains a consistent version comment format for auditability and Dependabot compatibility.

Why should I use commit SHAs instead of tags in GitHub Actions workflows?

Using commit SHAs instead of tags in GitHub Actions workflows prevents silent dependency changes from mutable tags. Pinning to immutable commit SHAs ensures workflow stability and security hardening by guaranteeing the executed code does not change unless manually updated.

Do I need the GitHub CLI to update GitHub Action workflow steps?

Yes, you need the GitHub CLI installed to resolve action tags to immutable commit SHAs. The Skill requires the GitHub CLI to query repository release and git reference metadata for accurate SHA pinning during CI/CD maintenance.

Can I automate CI/CD security hardening for existing repository workflows?

Yes, you can automate CI/CD security hardening for existing repository workflows. The Skill fetches the latest commit SHA for any GitHub Action, formats the uses line, and applies version tracking comments to prevent unauthorized dependency modifications.

What is the best way to track GitHub Action versions after pinning to a commit SHA?

The best way to track GitHub Action versions after pinning to a commit SHA is to maintain a consistent version comment format. This Skill automatically applies this format to ensure auditability and seamless compatibility with Dependabot updates.