Babysitter cicd-pipeline-generator

Generate CI/CD pipelines for SDK build and release

install

source · Clone the upstream repo

git clone https://github.com/a5c-ai/babysitter

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/specializations/sdk-platform-development/skills/cicd-pipeline-generator" ~/.claude/skills/a5c-ai-babysitter-cicd-pipeline-generator && rm -rf "$T"

manifest: library/specializations/sdk-platform-development/skills/cicd-pipeline-generator/SKILL.md

CI/CD Pipeline Generator Skill

Overview

This skill generates CI/CD pipelines for SDK build, test, and release workflows across multiple languages and platforms.

Capabilities

Generate GitHub Actions workflows
Generate GitLab CI/CD pipelines
Configure multi-language build matrices
Set up release automation
Implement quality gates and checks
Configure artifact publishing
Support monorepo workflows
Implement security scanning

Target Processes

SDK Versioning and Release Management
SDK Code Generation Pipeline
SDK Testing Strategy

Integration Points

GitHub Actions
GitLab CI/CD
CircleCI
Jenkins
Azure Pipelines

Input Requirements

Languages to build
Testing requirements
Release workflow
Publishing targets
Quality gate requirements

Output Artifacts

CI/CD workflow files
Build configurations
Release automation scripts
Quality gate definitions
Publishing configurations
Security scan integration

Usage Example

skill:
  name: cicd-pipeline-generator
  context:
    platform: github-actions
    languages:
      - typescript
      - python
      - go
    stages:
      - lint
      - test
      - build
      - publish
    qualityGates:
      coverage: 80%
      linting: required
      security: required
    release:
      trigger: tags
      semantic: true
    publishing:
      npm: true
      pypi: true
      goModule: true

Best Practices

Use matrix builds for efficiency
Implement proper quality gates
Automate releases with semantic versioning
Include security scanning
Cache dependencies appropriately
Use reusable workflow components