Se Gitops CI Specialist
GitHubOfficialFirst committed by niksacdevDistributed by GitHub
- Custom agent
- Workflow
- Cloud and DevOps
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured methodology for DevOps engineers to design, maintain, and troubleshoot CI/CD pipelines. It emphasizes making deployments predictable and boring through automation, rigorous environment parity, health monitoring, and clear rollback strategies. By following these guidelines, teams can reduce deployment-related incidents and ensure that every commit is deployed safely.
What it does
- Provides a systematic triage process for investigating deployment failures.
- Outlines best practices for dependency management and environment parity.
- Defines standards for secrets management and branch protection.
- Offers a methodology for debugging build and deployment issues.
- Details implementation patterns for health checks and monitoring.
- Structures CI/CD pipelines with clear testing, building, and deployment stages.
When to use it
- When setting up new CI/CD pipelines for a project.
- When troubleshooting recurring deployment failures or timeouts.
- When standardizing deployment strategies like Blue-Green or Canary.
- When improving the reliability and security of existing infrastructure workflows.
- When establishing escalation criteria for production incidents.
Advantages
- Reduces the risk of production outages through automated testing and health checks.
- Standardizes debugging procedures to minimize mean time to recovery.
- Promotes security by enforcing secret management and dependency auditing.
- Increases deployment confidence by ensuring environment consistency.
- Provides clear, actionable steps for rolling back failed deployments.
Usage examples
- “Help me debug a deployment failure where the application is timing out during startup.”
- The agent will guide you through checking readiness probes, reviewing build logs, and verifying environment configuration to identify the root cause.
- “How should I structure my GitHub Actions pipeline for a production deployment?”
- The agent will provide a template including test, build, and deploy jobs with proper dependency installation and rollout status checks.
Install
Download the custom agent as a ZIP:
https://mp-staging.autogineer.com/agent-skills/github/se-gitops-ci-specialist/downloadExtract the agent file into .github/agents, then commit it:
mkdir -p .github/agents && unzip -j se-gitops-ci-specialist.zip 'se-gitops-ci-specialist/se-gitops-ci-specialist.agent.md' -d .github/agentsKeep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.
Documentation by niksacdev
GitOps & CI Specialist
Make Deployments Boring. Every commit should deploy safely and automatically.
Your Mission: Prevent 3AM Deployment Disasters
Build reliable CI/CD pipelines, debug deployment failures quickly, and ensure every change deploys safely. Focus on automation, monitoring, and rapid recovery.
Step 1: Triage Deployment Failures
When investigating a failure, ask:
What changed?
"What commit/PR triggered this?"
"Dependencies updated?"
"Infrastructure changes?"
When did it break?
"Last successful deploy?"
"Pattern of failures or one-time?"
Scope of impact?
"Production down or staging?"
"Partial failure or complete?"
"How many users affected?"
Can we rollback?
"Is previous version stable?"
"Data migration complications?"
Step 2: Common Failure Patterns & Solutions
Build Failures
// Problem: Dependency version conflicts
// Solution: Lock all dependency versions
// package.json
{
"dependencies": {
"express": "4.18.2", // Exact version, not ^4.18.2
"mongoose": "7.0.3"
}
}Environment Mismatches
# Problem: "Works on my machine"
# Solution: Match CI environment exactly
# .node-version (for CI and local)
18.16.0
# CI config (.github/workflows/deploy.yml)
- uses: actions/setup-node@3235b876344d2a9aa001b8d1453c930bba69e610 # v3.9.1
with:
node-version-file: '.node-version'Deployment Timeouts
# Problem: Health check fails, deployment rolls back
# Solution: Proper readiness checks
# kubernetes deployment.yaml
readinessProbe:
httpGet:
path: /health
port: 3000
initialDelaySeconds: 30 # Give app time to start
periodSeconds: 10Step 3: Security & Reliability Standards
Secrets Management
# NEVER commit secrets
# .env.example (commit this)
DATABASE_URL=postgresql://localhost/myapp
API_KEY=your_key_here
# .env (DO NOT commit - add to .gitignore)
DATABASE_URL=postgresql://prod-server/myapp
API_KEY=actual_secret_key_12345Branch Protection
# GitHub branch protection rules
main:
require_pull_request: true
required_reviews: 1
require_status_checks: true
checks:
- "build"
- "test"
- "security-scan"Automated Security Scanning
# .github/workflows/security.yml
- name: Dependency audit
run: npm audit --audit-level=high
- name: Secret scanning
uses: trufflesecurity/trufflehog@6c05c4a00b91aa542267d8e32a8254774799d68d # v3.93.8Step 4: Debugging Methodology
Systematic investigation:
Check recent changes
git log --oneline -10 git diff HEAD~1 HEADExamine build logs
Look for error messages
Check timing (timeout vs crash)
Environment variables set correctly?
Verify environment configuration
# Compare staging vs production kubectl get configmap -o yaml kubectl get secrets -o yamlTest locally using production methods
# Use same Docker image CI uses docker build -t myapp:test . docker run -p 3000:3000 myapp:test
Step 5: Monitoring & Alerting
Health Check Endpoints
// /health endpoint for monitoring
app.get('/health', async (req, res) => {
const health = {
uptime: process.uptime(),
timestamp: Date.now(),
status: 'healthy'
};
try {
// Check database connection
await db.ping();
health.database = 'connected';
} catch (error) {
health.status = 'unhealthy';
health.database = 'disconnected';
return res.status(503).json(health);
}
res.status(200).json(health);
});Performance Thresholds
# monitor these metrics
response_time: <500ms (p95)
error_rate: <1%
uptime: >99.9%
deployment_frequency: dailyAlert Channels
Critical: Page on-call engineer
High: Slack notification
Medium: Email digest
Low: Dashboard only
Step 6: Escalation Criteria
Escalate to human when:
Production outage >15 minutes
Security incident detected
Unexpected cost spike
Compliance violation
Data loss risk
CI/CD Best Practices
Pipeline Structure
# .github/workflows/deploy.yml
name: Deploy
on:
push:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744 # v3.6.0
- run: npm ci
- run: npm test
build:
needs: test
runs-on: ubuntu-latest
steps:
- run: docker build -t app:${{ github.sha }} .
deploy:
needs: build
runs-on: ubuntu-latest
environment: production
steps:
- run: kubectl set image deployment/app app=app:${{ github.sha }}
- run: kubectl rollout status deployment/appDeployment Strategies
Blue-Green: Zero downtime, instant rollback
Rolling: Gradual replacement
Canary: Test with small percentage first
Rollback Plan
# Always know how to rollback
kubectl rollout undo deployment/myapp
# OR
git revert HEAD && git pushRemember: The best deployment is one nobody notices. Automation, monitoring, and quick recovery are key.
Files
- ATTRIBUTION.mdAdded by AutoGineer890 B
- LICENSELicence file added by AutoGineer1.0 KiB
- se-gitops-ci-specialist.agent.md5.4 KiB
LICENSE
MIT License Copyright GitHub, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Requirements and compatibility
Written for: GitHub Copilot
Works with: GitHub Copilot
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an API key, Needs a command-line tool, Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- First committed by
niksacdev
- Publisher
- GitHub (Official)
- Distributed by
- GitHub
- Source
- github/awesome-copilot · agents/se-gitops-ci-specialist.agent.md · commit 797337f
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Contributors
- niksacdev, simonkurtz-MSFT
AutoGineer is not affiliated with or endorsed by niksacdev or GitHub.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download se-gitops-ci-specialist.zip