github-actions

Automate GitHub Actions workflows for CI/CD, matrix testing, caching, secrets, and provenance publishing.

4|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/mcclowes/lea --skill github-actions-mcclowes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions
Source: https://github.com/mcclowes/lea/tree/main/.claude/skills/github-actions
Command: npx skills add https://github.com/mcclowes/lea --skill github-actions-mcclowes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides creating GitHub Actions workflows for CI/CD, test matrices, and release automation to streamline deployments.

Core Features & Use Cases

  • Matrix testing: Run tests across multiple Node versions
  • Caching & performance: Efficient caching of dependencies
  • Release automation: Publish with provenance and secure secrets

Quick Start

Add a workflow file to run tests on push and trigger a release process.

Frequently Asked Questions about github-actions

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

FAQPage Schema
How do I automate CI/CD pipelines with GitHub Actions?

GitHub Actions automate CI/CD by running workflows triggered on events like push or pull requests. Define workflow files in .github/workflows/ to run tests, build, and deploy automatically across your repository without external CI tools.

Can I run tests across multiple Node versions in GitHub Actions?

Matrix testing in GitHub Actions runs the same job across multiple Node versions simultaneously. Configure a matrix strategy in your workflow to test compatibility, catch version-specific bugs, and validate your package works on all supported Node releases.

How do I publish npm packages and VS Code extensions with provenance from GitHub Actions?

Provenance-enabled publishing verifies package authenticity by recording build metadata. Use GitHub Actions to sign and publish npm packages and VS Code extensions with cryptographic proof of origin, ensuring downstream users can validate the release came from your repository.

What's the best way to manage secrets and OIDC tokens in GitHub Actions workflows?

GitHub Actions securely handle secrets and OIDC tokens through environment configuration. Store credentials as repository secrets, reference them safely in workflows, and use OIDC for token-based authentication to eliminate long-lived credential management.

How do I improve GitHub Actions workflow performance with dependency caching?

Dependency caching in GitHub Actions stores node_modules or build artifacts between runs. Configure cache actions to restore dependencies on subsequent builds, reducing workflow duration and CI costs by skipping redundant downloads and installs.