github-actions-writer

GitHub Actions workflows automate CI/CD by running jobs on events like code pushes. Define a YAML file in .github/workflows/ specifying triggers, jobs, and steps. This Skill generates production-ready workflows with built-in security, caching, and performance optimization for any language or framework.

Best practices include least privilege permissions, OIDC-based deployments, pinned action versions, dependency caching, concurrency control, and timeouts. These prevent supply-chain attacks, reduce execution time, and ensure reliable deployments. This Skill applies all of them automatically to generated workflows.

Yes. GitHub Actions supports multi-job workflows that build, test, and deploy in sequence or parallel. You can cache dependencies between jobs, run matrix builds across languages and OS versions, and gate deployments on test success. This Skill templates this pattern for common stacks.

Optimize by caching dependencies, using matrix strategies to parallelize jobs, filtering runs by path changes, and setting appropriate timeouts. Concurrency control prevents redundant runs. This Skill incorporates these techniques to lower CI/CD costs and deployment latency.

GitHub Actions runs natively in GitHub repositories with no external platform needed, integrating seamlessly with code and pull requests. It offers free tier minutes and native support for GitHub-native security checks. Other platforms require external configuration; Actions workflows are version-controlled YAML files.

Enable debug logging in workflow settings, review job logs for step failures, check permissions and secrets, and validate YAML syntax. Common causes include missing environment variables, incorrect action versions, and permission scoping. This Skill provides references and guidance to resolve failures quickly.