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.
What this skill does
# 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 in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.