Agent skill · software engineering · sickn33
github-actions-templates
Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications.
Why this skill is useful
Provides specific GitHub Actions workflow patterns for CI/CD that enhance automation capabilities beyond generic knowledge.
What it needs
Requires docker, kubectl installed locally. Requires aws, github account access. About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
GitHub Actions Workflow Patterns When to Use Implement testing, matrix builds, artifact preparation or an explicitly authorized deployment workflow for an existing repository. Inputs Inspect the repository's actual scripts, lockfile, supported runtimes, required check names and release policy. Read resources/implementation-playbook.md and references/common-workflows.md before choosing job boundaries. Test Workflow This Node example assumes the target repository declares npm test and supports Node 22. Adapt the runtime and command to the actual project. The pinned action revisions are explicit review inputs; verify them before adopting or updating the template. Matrix Builds Add a matrix only for versions and operating systems the project supports. Keep dependencies reproducible, identify failing combinations, and avoid hiding failures with blanket continue-on-error. Test required-check behavior when jobs are conditionally skipped. Build and Publication Build an artifact from the tested commit and record its identity. Publication needs a separate trusted job with the minimum registry permission. Do not publish artifacts produced by arbitrary untrusted code in a privileged context; bind accepted artifacts to their exact source and producing workflow. Deployment Use the project's protected release path. Identify the immutable artifact, destination, workload identity, rollout and rollback checks before adding deployment commands. A named GitHub environment does not configure reviewers automatically. Verify its actual protections. Do not label a placeholder echo command as a successful deployment. Verification Exercise one passing change and one deliberate test failure on a topic branch. Confirm the failing check prevents downstream publication. Inspect tokens, runner isolation, caches and artifact boundaries. Keep production credentials absent from untrusted validation jobs. Example A project needs Linux and Windows tests. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/github-actions-templates--952d5a