github-actions-templates

Create GitHub Actions workflows for testing, building, and deploying applications.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill github-actions-templates-surfingalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-templates
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/github-actions-templates
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill github-actions-templates-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve? Writing CI/CD pipelines from scratch is error-prone: YAML indentation bugs, misused secrets, wrong permissions, and broken matrix strategies cause silent workflow failures. This Skill provides tested GitHub Actions workflow patterns and documents the real failure modes so pipelines work on the first push. ## Core Features & Use Cases - Ready-to-use workflow patterns: Test workflows with matrix Node versions, Docker build-and-push to ghcr.io, Kubernetes deployment via AWS EKS, multi-OS matrix builds, reusable workflows, security scanning with Trivy/Snyk, and production deploys with approval gates. - Common pitfalls guide: Documents concrete failure modes including YAML syntax errors, secret handling mistakes, GITHUB_TOKEN permission gaps, matrix exclude/include bugs, and stale cache issues, each with wrong-vs-correct examples. - Use Case: You need to set up CI for a Node.js repo. Ask for a test workflow, and get a complete YAML with checkout, setup-node caching, lint, test, and Codecov upload, plus guidance on avoiding cache-key mistakes. ## Quick Start Ask the assistant to create a GitHub Actions workflow that runs tests on Node 18 and 20 for every pull request.

Frequently Asked Questions about github-actions-templates

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

FAQPage Schema
How do I create a GitHub Actions workflow for Node.js testing?

Use a workflow triggered on push and pull_request with actions/checkout, actions/setup-node with cache: npm, then run npm ci, lint, and test steps. A matrix strategy over node-version 18.x and 20.x tests multiple runtimes in parallel.

How to build and push Docker images in GitHub Actions?

Use docker/login-action to authenticate to ghcr.io with GITHUB_TOKEN, docker/metadata-action to generate tags, and docker/build-push-action with cache-from and cache-to set to type=gha. The job needs packages: write permission.

Why are my GitHub Actions secrets empty in if conditions?

Secrets are not available in if: conditionals; they only resolve in env: blocks at job or step level. Move the secret into an env variable and reference that in your condition or script instead.

Why does GitHub Actions caching not work for node_modules?

Cache misses happen when the key lacks a lockfile hash or the wrong path is cached. Include hashFiles('**/package-lock.json') in the key, or use the built-in cache: npm option in actions/setup-node.

Can GITHUB_TOKEN trigger other workflows or access other repos?

No. GITHUB_TOKEN cannot trigger repository_dispatch events and only has access to the current repository. Use a Personal Access Token stored in secrets for cross-repo clones or workflow dispatch calls.