github-actions-workflows
GitHub Actions workflow patterns for CI/CD including matrix builds, reusable workflows, secrets management, and caching strategies. Use when setting up or optimizing GitHub Actions pipelines.
Best use case
github-actions-workflows is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
GitHub Actions workflow patterns for CI/CD including matrix builds, reusable workflows, secrets management, and caching strategies. Use when setting up or optimizing GitHub Actions pipelines.
Teams using github-actions-workflows should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/github-actions-workflows/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-actions-workflows Compares
| Feature / Agent | github-actions-workflows | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
GitHub Actions workflow patterns for CI/CD including matrix builds, reusable workflows, secrets management, and caching strategies. Use when setting up or optimizing GitHub Actions pipelines.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GitHub Actions Workflows Expert guidance for designing reliable, secure, and performant GitHub Actions CI/CD pipelines with patterns for matrix builds, reusable workflows, caching, and deployment automation. ## When to Use This Skill - Setting up CI/CD pipelines with GitHub Actions from scratch - Optimizing slow or expensive GitHub Actions workflows - Implementing matrix builds for multi-environment testing - Creating reusable workflows and composite actions for DRY pipelines - Managing secrets securely across environments - Configuring caching for dependency and build artifact reuse - Setting up deployment workflows with staging and production gates - Debugging failing or flaky workflow runs - Implementing concurrency controls to prevent duplicate runs ## Quick Reference | Task | Load reference | | --- | --- | | Matrix builds, reusable workflows, caching, deployment, concurrency | `skills/github-actions-workflows/references/workflow-patterns.md` | ## Core Principles - **Structured jobs**: Break workflows into clear, distinct jobs with defined dependencies - **DRY configuration**: Use reusable workflows and composite actions to avoid duplication - **Security first**: Use GitHub secrets, OIDC, and minimum necessary permissions - **Cache aggressively**: Cache dependencies, build outputs, and test fixtures - **Trigger thoughtfully**: Configure event triggers to avoid unnecessary workflow runs - **Document workflows**: Add comments explaining non-obvious YAML configuration ## Workflow ### 1. Design Plan the pipeline structure before writing YAML. - Identify trigger events (push, pull_request, schedule, workflow_dispatch) - Map job dependencies and what can run in parallel - Determine caching opportunities (dependencies, build outputs) - Plan environment promotion (dev, staging, production) ### 2. Implementation Build the pipeline incrementally. - Start with a minimal workflow and add complexity - Use matrix builds for multi-environment testing - Extract reusable workflows for shared patterns - Configure secrets management with environment protection ### 3. Optimization Reduce runtime and cost. - Profile workflow timing to identify bottlenecks - Add caching for dependencies and build artifacts - Use concurrency controls to cancel redundant runs - Configure path filters to skip unaffected workflows ### 4. Maintenance Keep workflows healthy over time. - Pin action versions to specific SHAs for security - Review and update actions regularly - Monitor workflow runtime trends and costs - Peer-review workflow changes before merging ## Common Mistakes - Using `actions/checkout@main` instead of pinning to a SHA or version tag - Not setting `permissions` block (defaults to overly broad read-write) - Caching node_modules instead of the package manager cache directory - Missing `concurrency` groups, leading to duplicate deploys - Hardcoding secrets in workflow files instead of using GitHub Secrets - Running the full test suite on every push instead of using path filters - Not using `workflow_call` for shared CI logic across repositories
Related Skills
gitops-workflows
GitOps workflows and patterns using ArgoCD and Flux for declarative Kubernetes deployments. Use when implementing CI/CD for Kubernetes, managing multi-environment deployments, or adopting declarative infrastructure practices.
dev-workflows
Use when running builds, executing tests, or improving developer experience workflows - provides structured guidance for build/test execution and DX improvement.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
workflow-security-audit
Comprehensive security assessment and remediation. Use for security reviews, compliance checks, vulnerability assessments.
workflow-performance
Systematic performance analysis and optimization. Use when things are slow, need optimization, or preparing for scale.
workflow-feature
Complete feature development workflow from design to deployment. Use when implementing new features or functionality.
workflow-feature-development
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
workflow-bug-fix
Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.
wiring-audit
User-triggered audit that finds wiring drift between a project's UI surfaces and backend capabilities — orphan surfaces (UI calls endpoints/hooks/procedures that no longer exist), unwired capabilities (backend routes/exports that nothing surfaces), shape drift (both exist but contracts mismatch), method drift (URL matches, HTTP verb does not), validation drift (frontend vs backend rules diverged), permission drift (UI exposes what backend forbids or vice versa), stale labels (UI text references renamed backend concepts), and unsurfaced configuration (env vars or flags that gate behavior with no UI or CLI to control them). This skill should be used when the user asks to "audit our wiring," "find UI/backend drift," "find unwired capabilities," "find stale surfaces," "check for contract violations," "find unused endpoints," "find unused hooks," "what mismatches between UI and backend," or any similar request whose deliverable is a prioritized findings report rather than a descriptive snapshot. Generic across UI frameworks but optimized for React applications (hooks, fetch, react-query, SWR, tRPC, server actions, react-router, Next.js). Not for descriptive architectural snapshots (use architectural-analysis), security audits (use security-auditor), or performance audits (use workflow-performance).
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-researcher
Use this skill when you need to research a topic online, gather information from multiple sources, or evaluate source credibility. Trigger phrases: 'research', 'find information about', 'look up', 'investigate'. Not for academic systematic reviews (use literature-reviewer) or fact-checking specific claims (use fact-checker).
visual-modes
Use when activating visual showcase modes (supersaiyan, kamehameha, over9000) for UI or interaction design - provides mode-specific enhancement checklists.