github-actions-builder_skill
- TypeScript
4
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill dexploarer/claudius-skills --skill github-actions-builder- SKILL.md14.3 KB
Overview
This skill creates GitHub Actions workflows for CI/CD: testing, building, deploying, releasing, and container workflows. It generates common and framework-specific YAML workflows, detects project type, and wires up best practices like caching, matrix testing, and secret handling. Use it to quickly bootstrap reliable automation for Node, Python, Go, Docker, and common frameworks.
How this skill works
The skill inspects repository files to detect project type (package.json, requirements.txt, go.mod, Dockerfile, Gemfile) and creates a .github/workflows directory with tailored workflow YAML files. Templates include test on PR, build-and-deploy, release automation, Docker build/push, framework-specific flows (Next.js, Django, Go), and advanced patterns like matrix testing and reusable workflows. It also outlines required secrets and provides speed, security, and notification patterns.
When to use it
- When you need to setup GitHub Actions CI/CD quickly
- To create workflows that run tests, linters, and builds on push/PR
- When you want automated deploys on merge to main or staging
- To add release pipelines that publish packages or create GitHub releases
- When you need Docker image build-and-push or container registry automation
Best practices
- Detect project type and apply framework-specific templates (Next.js, Django, Go)
- Cache dependencies and build outputs to speed up pipelines (actions/cache, setup-node pip cache)
- Use npm ci / pip install -r requirements.txt or go mod download for reproducible installs
- Fail fast in matrix jobs and run security scans (CodeQL, dependency-review)
- Store sensitive tokens in repository secrets and limit job permissions
Example use cases
- Run lint, type-check, unit tests and coverage on every pull request for a Node.js app
- Build a production artifact and deploy to Vercel on pushes to main using VERCEL_* secrets
- Publish npm packages automatically on tag pushes and create a GitHub release
- Build and push Docker images to GitHub Container Registry on tags and main branch
- Run matrix tests across multiple OS and Node/Go versions for broader coverage
FAQ
Common secrets: NPM_TOKEN, VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, DOCKERHUB_USERNAME, DOCKERHUB_TOKEN, CODECOV_TOKEN, SLACK_WEBHOOK_URL.
How do I speed up workflow runs?
Cache dependencies (setup-node cache or actions/cache), use npm ci, reuse build caches for Docker, and enable matrix fail-fast to reduce wasted work.
