JiayiV/question_mixing / skills/agent-se-gitops-ci-specialist
SE: DevOps/CI
UnverifiedDevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable
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: 10
Step 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_12345
Branch 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.8
Step 4: Debugging Methodology
Systematic investigation:
-
Check recent changes
git log --oneline -10 git diff HEAD~1 HEAD -
Examine 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 yaml -
Test 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: daily
Alert 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/app
Deployment 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 push
Remember: The best deployment is one nobody notices. Automation, monitoring, and quick recovery are key.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |