pinned-tag

Replace unpinned GitHub Actions tags with commit SHAs using git ls-remote.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dallay/cvix --skill pinned-tag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pinned-tag
Source: https://github.com/dallay/cvix/tree/main/.agents/skills/pinned-tag
Command: npx skills add https://github.com/dallay/cvix --skill pinned-tag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pinning GitHub Actions tags to specific commit SHAs prevents mutable references from breaking builds and reduces supply-chain risk.

Core Features & Use Cases

  • Resolve and replace: find tags in workflows and replace them with the corresponding full commit SHAs.
  • Auditing and verification: scan manifests and workflow files to identify unpinned tags and report potential risks.
  • Commit policy guidance: provide a safe workflow for applying patches with explicit commit approval.

Quick Start

Use this skill to pin a v2 action to its commit SHA in your workflow.

Frequently Asked Questions about pinned-tag

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

FAQPage Schema
How do I pin GitHub Actions tags to commit SHAs in workflows?

Pin GitHub Actions tags by resolving them to their corresponding full commit SHAs using git ls-remote, then replacing mutable references in your CI workflows to enforce immutability.

Why should I pin GitHub Actions to specific commit SHAs?

Pinning GitHub Actions to specific commit SHAs prevents mutable references from breaking builds and reduces supply-chain risk across your repository workflows and dependency manifests.

How can I scan workflows for unpinned tags?

Scan workflows for unpinned tags by auditing manifest and workflow files to identify unpinned tags and report potential supply-chain risks associated with mutable references.

Can I use this to update dependency manifests across multiple repositories?

Yes, you can update dependency manifests across multiple repositories. The skill applies to CI workflows and dependency manifests across repositories, replacing tags with verified commit SHAs.

How does the skill verify a resolved SHA belongs to the expected tag?

The skill verifies a resolved SHA belongs to the expected tag by using git ls-remote to resolve the tag and checking the resolved commit SHA before applying any workflow changes.