ci-config-helper
Scannednpx machina-cli add skill k1lgor/virtual-company/08-ci-config-helper --openclawCI/Config Helper
You help users set up or improve CI/CD pipelines and automation configs in a clean, secure way.
When to use this skill
- User asks: "Set up CI for this repo", "Create a GitHub Actions workflow", "Add a linter step."
- User mentions: deployment, testing automation, or project-level configuration.
How to use it
- Detect the environment:
- Platform: GitHub Actions, GitLab CI, CircleCI, Bitbucket, or generic scripts.
- Language: Node, Python, Go, Java, etc.
- Ask or infer:
- What should the pipeline do? (lint, test, build, deploy)
- Where are tests run? (command(s) to run them)
- Any required environment variables, secrets, or services?
- Generate configs that:
- Use widely recommended actions/templates where possible.
- Avoid exposing secrets in logs or configs.
- Include clear comments explaining each major step.
- Suggest improvements:
- Add caching for dependencies.
- Parallelize independent jobs if it helps speed.
- Add notifications for failures (if appropriate).
- Keep configs readable:
- Prefer shorter, well-commented configs over overly complex ones.
Examples
User Request: "Create a GitHub Action to run tests on push."
Agent Action/Output:
name: CI
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Setup Node
uses: actions/setup-node@v3
with:
node-version: "18"
cache: "npm"
- run: npm ci
- run: npm test
User Request: "Add a linting step to my GitLab CI."
Agent Action/Output:
lint:
stage: test
image: python:3.9
script:
- pip install flake8
- flake8 . --count --max-line-length=88
Source
git clone https://github.com/k1lgor/virtual-company/blob/main/skills/08-ci-config-helper/SKILL.mdView on GitHub Overview
CI/CD config helper assists users in setting up or improving CI/CD pipelines and automation configs across GitHub Actions, GitLab CI, CircleCI, Bitbucket, or generic scripts. It emphasizes simple, readable, and secure configurations with clear comments and careful handling of secrets.
How This Skill Works
It first detects the environment by platform and language, then asks or infers pipeline goals such as lint, test, build, or deploy. It generates configs using widely recommended templates, includes comments for major steps, and avoids exposing secrets; it also suggests improvements like caching, parallelization, and notifications.
When to Use It
- Set up CI for a new repository
- Create a GitHub Actions workflow
- Add a linting or testing step to an existing pipeline
- Configure CI for multiple platforms (GitHub Actions, GitLab CI, CircleCI)
- Improve an existing pipeline with caching, parallel jobs, and failure alerts
Quick Start
- Step 1: Identify the target platform and language for the repository
- Step 2: Define pipeline goals such as lint, test, build, and deploy commands
- Step 3: Generate a secure, readable config with clear comments and review for secrets
Best Practices
- Use established actions and templates where possible
- Keep secrets out of logs and configs; use encrypted secrets or vaults
- Comment major steps to explain intent and decisions
- Enable dependency caching to speed up builds
- Parallelize independent jobs and add failure notifications
Example Use Cases
- GitHub Actions workflow to install dependencies and run tests on push
- GitLab CI YAML to install Python deps and run flake8 and pytest
- CircleCI config for a Node.js project with npm ci and test
- Bitbucket Pipelines configuration for a JavaScript project with caching
- Generic shell-based CI script that runs lint, test, and build steps across environments
