- Home
- Skills
- Wesleysmits
- Agent Skills
- Cicd Config Builder
cicd-config-builder_skill
2
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 wesleysmits/agent-skills --skill cicd-config-builder- SKILL.md6.8 KB
Overview
This skill generates or updates CI/CD pipeline configurations for GitHub Actions, GitLab CI, or CircleCI. It detects your project type, builds an appropriate pipeline (install → lint → test → build → deploy), and outputs ready-to-apply YAML with validation steps and deployment hooks. Use it to get a working CI/CD workflow tailored to your framework and package manager.
How this skill works
The skill scans the repository for framework indicators (Next.js, Nuxt, Vite, Node, Python, static) and package manager locks or manifest files. It detects existing CI config files and selects the target platform, then determines required stages based on scripts and dev dependencies. Finally it generates platform-specific YAML, includes caching, matrix support, and optional deployment steps, and suggests local validation commands.
When to use it
- Setting up CI/CD for a new or existing project
- Creating GitHub Actions workflows, .gitlab-ci.yml, or CircleCI config
- Adding lint, test, build, or deploy steps to pipelines
- Automating deployments to Vercel, S3, or other targets
- Validating or updating an existing pipeline configuration
Best practices
- Detect project framework and package manager before generating config
- Include lint and test stages when ESLint or a test runner is present
- Use caching for node_modules/npm to speed builds and reduce costs
- Prefer matrix jobs for testing multiple Node versions when relevant
- Document required secret names and ensure they exist in repo settings
- Validate generated YAML locally with actionlint, circleci, or GitLab linter
Example use cases
- Create a GitHub Actions workflow for a Next.js app with lint, test, and build steps
- Add a GitLab CI pipeline for a Node.js service that caches npm and uploads build artifacts
- Generate a CircleCI config using the node orb and a single build-and-test job
- Append a deploy job for Vercel or AWS S3 that runs only on the main branch
- Produce a matrix job to test Node 18, 20, and 22 across unit tests
FAQ
It checks for existing config files and the repository host; default is GitHub Actions for GitHub repos unless the user specifies otherwise.
Can it add deployment steps for my provider?
Yes. It includes example deploy jobs for Vercel and AWS S3 and can be adapted to other targets by adding the required actions and secrets.
How do I validate the generated config?
Use actionlint for GitHub Actions, the GitLab CI Lint API or local tool for GitLab, and circleci config validate for CircleCI; also run a YAML linter.