github-actions
GitHub Actions workflow authoring for CI/CD pipelines. Covers workflow syntax, triggers, jobs, steps, matrix strategies, caching, artifacts, reusable workflows, composite actions, secrets management, OIDC authentication, and permissions hardening. Use when creating workflows, configuring jobs, setting up caching, or automating releases. Use for github-actions, workflow, ci, cd, actions, jobs, steps, matrix, cache, artifact, secrets, reusable-workflow.
What this skill does
# GitHub Actions
## Overview
GitHub Actions is a CI/CD platform that automates build, test, and deployment pipelines directly from GitHub repositories. Workflows are YAML files in `.github/workflows/` triggered by events like pushes, pull requests, schedules, or manual dispatch. Each workflow contains one or more jobs that run on GitHub-hosted or self-hosted runners.
**When to use:** Automated testing, continuous deployment, release automation, scheduled tasks, multi-platform builds, dependency updates, container publishing, code quality checks, security scanning.
**When NOT to use:** Long-running services (use a proper hosting platform), heavy compute tasks exceeding runner limits (6-hour job timeout), tasks requiring persistent state between runs (use external storage), real-time event processing (use webhooks with a server).
## Quick Reference
| Pattern | Syntax / Action | Key Points |
| ------------------- | ------------------------------------------------ | ------------------------------------------- |
| Push trigger | `on: push: branches: [main]` | Filter by branch, path, or tag |
| PR trigger | `on: pull_request: types: [opened, synchronize]` | Defaults to opened, synchronize, reopened |
| Scheduled trigger | `on: schedule: - cron: '0 6 * * 1'` | UTC only, minimum 5-minute interval |
| Manual trigger | `on: workflow_dispatch: inputs:` | Define typed inputs for manual runs |
| Job dependencies | `needs: [build, test]` | Run jobs in sequence or parallel |
| Conditional job | `if: github.ref == 'refs/heads/main'` | Expression-based job/step filtering |
| Matrix strategy | `strategy: matrix: node: [18, 20, 22]` | Generates jobs for each combination |
| Dependency cache | `actions/cache@v5` | Hash-based keys with restore-keys fallback |
| Setup with cache | `actions/setup-node@v6` with `cache: 'pnpm'` | Built-in caching for package managers |
| Upload artifact | `actions/upload-artifact@v4` | Share data between jobs or preserve outputs |
| Download artifact | `actions/download-artifact@v4` | Retrieve artifacts from earlier jobs |
| Reusable workflow | `uses: ./.github/workflows/reusable.yml` | Called with `workflow_call` trigger |
| Composite action | `action.yml` with `using: composite` | Bundle multiple steps into one action |
| Concurrency | `concurrency: group: ${{ github.ref }}` | Cancel or queue duplicate runs |
| Environment secrets | `${{ secrets.API_KEY }}` | Scoped to repo, org, or environment |
| OIDC authentication | `permissions: id-token: write` | Short-lived tokens for cloud providers |
| Step outputs | `echo "key=value" >> "$GITHUB_OUTPUT"` | Pass data between steps and jobs |
| Service containers | `services: postgres: image: postgres:16` | Sidecar containers for integration tests |
| Timeout | `timeout-minutes: 30` | Fail fast on hung jobs or steps |
| Attestations | `actions/attest-build-provenance@v3` | SLSA build provenance for supply chain |
## Expressions and Contexts
| Context | Example | Description |
| --------- | ------------------------------- | ----------------------------------------- |
| `github` | `github.ref_name`, `github.sha` | Event metadata, repo info, actor |
| `env` | `env.NODE_ENV` | Environment variables at current scope |
| `secrets` | `secrets.API_KEY` | Encrypted secrets (masked in logs) |
| `inputs` | `inputs.environment` | Workflow dispatch or reusable inputs |
| `matrix` | `matrix.node` | Current matrix combination values |
| `steps` | `steps.build.outputs.version` | Outputs from previous steps |
| `needs` | `needs.prepare.outputs.tag` | Outputs from dependent jobs |
| `runner` | `runner.os`, `runner.arch` | Runner environment info |
| `vars` | `vars.DEPLOY_URL` | Repository or org configuration variables |
## Common Mistakes
| Mistake | Correct Pattern |
| -------------------------------------------- | -------------------------------------------------------------------------- |
| Using outdated action major versions | Pin to current major version (`@v6`) or commit SHA |
| Missing `persist-credentials: false` | Set on checkout when using custom tokens or OIDC |
| Broad `permissions` at workflow level | Set `permissions: {}` at workflow level, grant per-job |
| Cache key without dependency file hash | Include `hashFiles('**/pnpm-lock.yaml')` in cache key |
| Secrets in `if:` conditions | Secrets cannot be used in `if:` expressions directly |
| Using `pull_request_target` carelessly | Never run PR code with write permissions from `pull_request_target` |
| Not cancelling stale runs | Use `concurrency` with `cancel-in-progress: true` |
| Storing structured data as a single secret | Create individual secrets per value for proper log redaction |
| Referencing action tags without SHA pinning | Pin third-party actions to full commit SHA for supply chain safety |
| Hardcoding runner OS in scripts | Use `runner.os` context for cross-platform compatibility |
| Using `actions/cache` without `restore-keys` | Always provide restore-keys for partial cache matches |
| Interpolating user input in `run:` blocks | Pass untrusted values through `env:` to prevent script injection |
| No `timeout-minutes` on jobs | Set explicit timeouts to fail fast on hung processes |
| Using `always()` without scoping | Combine with status checks: `if: always() && steps.x.outcome == 'success'` |
## Delegation
- **Workflow debugging**: Use `Explore` agent to inspect workflow run logs
- **Security auditing**: Use `Task` agent to review permissions and secret usage
- **Code review**: Delegate to `code-reviewer` agent for workflow PR reviews
## References
- [Workflow syntax, triggers, jobs, steps, and concurrency](references/workflow-syntax.md)
- [Caching strategies and artifact management](references/caching-and-artifacts.md)
- [Matrix strategies, reusable workflows, and composite actions](references/matrix-and-reusable.md)
- [Security, secrets, OIDC, and permissions hardening](references/security-and-secrets.md)
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.