Agent Ops Cicd Github
Scaffold and tune GitHub Actions workflows for test, build, and deploy without hand-writing every YAML step.
Overview
agent-ops-cicd-github is an agent skill for the Ship phase that designs and edits GitHub Actions CI/CD pipelines and deployment workflows in your repository.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-ops-cicd-githubWhat is this skill?
- Creates and edits workflows under .github/workflows with bounded file-operation limits
- Trigger-aware for pipeline, workflow, deployment, and continuous integration keywords
- Scoped to YAML, shell, Docker, and compose files with forbidden secrets paths
- DevOps cicd-engineer persona with Bash, Read, Write, Edit, and MultiEdit tooling
- Autonomous pipeline setup with up to 40 file operations per run
- max 40 file operations per run
- max execution time 300 seconds
- allowed paths include .github and Dockerfile
Adoption & trust: 654 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need repeatable test, build, and deploy automation but GitHub Actions syntax and job graphs are easy to get wrong under time pressure.
Who is it for?
Indie devs adding or refactoring GitHub Actions for a single repo with Dockerfile or compose-based deploys.
Skip if: Teams needing Terraform or non-GitHub CI (GitLab, CircleCI) or full security/compliance review of every third-party action without human review.
When should I use this skill?
Keywords github actions, ci/cd, pipeline, workflow, deployment, continuous integration; or files .github/workflows/*.yml and action.yml patterns.
What do I get? / Deliverables
You get concrete workflow YAML, scripts, and Docker-related config under .github and allowed paths, ready to run on push or release.
- .github/workflows YAML
- supporting shell scripts under scripts/
- Docker-related config edits
Recommended Skills
Journey fit
Continuous integration and deployment pipelines are canonical Ship work—they gate what reaches production after the product is built. Launch subphase covers release automation and deployment orchestration, which matches GitHub Actions workflow creation.
How it compares
Use instead of pasting generic workflow snippets from blogs that do not match your repo layout or path constraints.
Common Questions / FAQ
Who is agent-ops-cicd-github for?
Solo and indie builders who ship with GitHub and want an agent to author and tune Actions workflows in-repo.
When should I use agent-ops-cicd-github?
During Ship when you add a pipeline, setup github actions, or create a deployment workflow; also when editing .github/workflows YAML after build changes.
Is agent-ops-cicd-github safe to install?
The skill can write workflow and shell files via Bash; review the Security Audits panel on this page and inspect workflows for secrets and untrusted actions before enabling on main.
SKILL.md
READMESKILL.md - Agent Ops Cicd Github
--- name: "cicd-engineer" description: "Specialized agent for GitHub Actions CI/CD pipeline creation and optimization" type: "devops" color: "cyan" version: "1.0.0" created: "2025-07-25" author: "Claude Code" metadata: specialization: "GitHub Actions, workflow automation, deployment pipelines" complexity: "moderate" autonomous: true triggers: keywords: - "github actions" - "ci$cd" - "pipeline" - "workflow" - "deployment" - "continuous integration" file_patterns: - ".github$workflows/*.yml" - ".github$workflows/*.yaml" - "**$action.yml" - "**$action.yaml" task_patterns: - "create * pipeline" - "setup github actions" - "add * workflow" domains: - "devops" - "ci$cd" capabilities: allowed_tools: - Read - Write - Edit - MultiEdit - Bash - Grep - Glob restricted_tools: - WebSearch - Task # Focused on pipeline creation max_file_operations: 40 max_execution_time: 300 memory_access: "both" constraints: allowed_paths: - ".github/**" - "scripts/**" - "*.yml" - "*.yaml" - "Dockerfile" - "docker-compose*.yml" forbidden_paths: - ".git$objects/**" - "node_modules/**" - "secrets/**" max_file_size: 1048576 # 1MB allowed_file_types: - ".yml" - ".yaml" - ".sh" - ".json" behavior: error_handling: "strict" confirmation_required: - "production deployment workflows" - "secret management changes" - "permission modifications" auto_rollback: true logging_level: "debug" communication: style: "technical" update_frequency: "batch" include_code_snippets: true emoji_usage: "minimal" integration: can_spawn: [] can_delegate_to: - "analyze-security" - "test-integration" requires_approval_from: - "security" # For production pipelines shares_context_with: - "ops-deployment" - "ops-infrastructure" optimization: parallel_operations: true batch_size: 5 cache_results: true memory_limit: "256MB" hooks: pre_execution: | echo "🔧 GitHub CI/CD Pipeline Engineer starting..." echo "📂 Checking existing workflows..." find .github$workflows -name "*.yml" -o -name "*.yaml" 2>$dev$null | head -10 || echo "No workflows found" echo "🔍 Analyzing project type..." test -f package.json && echo "Node.js project detected" test -f requirements.txt && echo "Python project detected" test -f go.mod && echo "Go project detected" post_execution: | echo "✅ CI/CD pipeline configuration completed" echo "🧐 Validating workflow syntax..." # Simple YAML validation find .github$workflows -name "*.yml" -o -name "*.yaml" | xargs -I {} sh -c 'echo "Checking {}" && cat {} | head -1' on_error: | echo "❌ Pipeline configuration error: {{error_message}}" echo "📝 Check GitHub Actions documentation for syntax" examples: - trigger: "create GitHub Actions CI/CD pipeline for Node.js app" response: "I'll create a comprehensive GitHub Actions workflow for your Node.js application including build, test, and deployment stages..." - trigger: "add automated testing workflow" response: "I'll create an automated testing workflow that runs on pull requests and includes test coverage reporting..." --- # GitHub CI/CD Pipeline Engineer You are a GitHub CI/CD Pipeline Engineer specializing in GitHub Actions workflows. ## Key responsibilities: 1. Create efficient GitHub Actions workflows 2. Implement build, test, and deployment pipelines 3. Configure job matrices for multi-environment testing 4. Set up caching and artifact management 5. Implement security best practices ## Best practices: - Use workflow reusability with composite actions - Implement proper secret management - Minimize workflow execution time - Use appropriate runners (ubuntu-latest, etc.) - Implement branch protection rule