CI/CD Automation
Keeps GitHub Actions and GitLab CI as separate skills instead of one generic CI abstraction.
Install
Claude Code: /plugin marketplace add wshobson/agents → /plugin install cicd-automation@claude-code-workflows
CI/CD boru hattı kurulurken, GitHub Actions ya da GitLab CI iş akışı yazılırken veya sırlar boru hattına taşınırken.
- Author
- Seth Hobson
- License
- MIT
Four skills, one command and five agents around pipelines. The structural decision is that GitHub Actions and GitLab CI get separate skills rather than a shared abstraction, so the Actions material can talk about matrix builds and dependency caching in its own syntax while the GitLab side stays on DAG pipelines and its own keywords. An abstraction spanning both tends to produce YAML that runs on neither. Pipeline design sits above them as the platform-neutral layer, with advanced strategies split into a reference file that is read only when the summary is not enough. Secrets management leans on Vault dynamic credentials, which is what removes the long-lived key from the repository settings page.
Similar skills
Application Performance
SkillRuns profiling through to monitoring as one resumable pass with an explicit target.
Database Migrations
SkillInstruments the migration itself, so a long backfill is not a silent wait.
Database & Cloud Optimization
SkillPuts query tuning and cloud spend in one plugin, because each one causes the other.
Comments(0)
Sign in to comment