agent-ops-cicd-github
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Required · GitHub
- Operating systems
- Linux · Docker
- Runtime requirements
- Node.js · Python · Docker
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agent-ops-cicd-github
description: Agent skill for ops-cicd-github - invoke with $agent-ops-cicd-github name: "cicd-engineer" descr…
category: ai
runtime: Node.js / Python / Docker
---
# agent-ops-cicd-github output preview
## PART A: Task fit
- Use case: Agent skill for ops-cicd-github - invoke with $agent-ops-cicd-github name: "cicd-engineer" description: "Specialized agent for GitHub Actions CI/CD pipeline creation and optimization" version: "1.0.0" requires GitHub API key; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Key responsibilities: / Best practices: / Workflow patterns:” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for ops-cicd-github - invoke with $agent-ops-cicd-github name: "cicd-engineer" description: "Specialized agent for GitHub Actions CI/CD pipeline creation and optimization" version: "1.0.0" requires GitHub API key; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Key responsibilities: / Best practices: / Workflow patterns:” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; may access external network resources; requires GitHub API keys.
## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; requires GitHub API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Key responsibilities: / Best practices: / Workflow patterns:”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-ops-cicd-github
description: Agent skill for ops-cicd-github - invoke with $agent-ops-cicd-github name: "cicd-engineer" descr…
category: ai
source: ruvnet/ruflo
---
# agent-ops-cicd-github
## When to use
- Agent skill for ops-cicd-github - invoke with $agent-ops-cicd-github name: "cicd-engineer" description: "Specialized a…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Key responsibilities: / Best practices: / Workflow patterns:” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; may access external network resources; requires GitHub API keys.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-ops-cicd-github" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Key responsibilities: / Best practices: / Workflow patterns:
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js / Python / Docker | read files, write/modify files, run shell commands | may access external network resources
guardrails -> requires GitHub API keys + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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:
- Create efficient GitHub Actions workflows
- Implement build, test, and deployment pipelines
- Configure job matrices for multi-environment testing
- Set up caching and artifact management
- 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 rules
- Cache dependencies effectively
Workflow patterns:
name: CI/CD Pipeline
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions$checkout@v4
- uses: actions$setup-node@v4
with:
node-version: '18'
cache: 'npm'
- run: npm ci
- run: npm testSecurity considerations:
- Never hardcode secrets
- Use GITHUB_TOKEN with minimal permissions
- Implement CODEOWNERS for workflow changes
- Use environment protection rules
Decide Fit First
Design Intent
How To Use It
Boundaries And Review