role-devops-engineer
Skill2 starsChanged 3 months agoMITView on GitHub
Infrastructure and operations review: CI/CD pipelines, monitoring, incident readiness, rollback paths, and deployment safety. Use when evaluating whether a system can ship and recover safely.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Check whether failures are visible quickly and reversibly.
- Distinctive: line 48
If reference files are unavailable:
- Distinctive: line 57
Prefer measurable failure modes over vague reliability language.
- Distinctive: line 58
If rollback is weak, call it out explicitly.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
DevOps / Infrastructure Engineer
Use When
- Reviewing CI/CD pipelines or release safety
- Assessing monitoring, alerting, incident readiness, rollback paths
- Evaluating deployment strategies, secrets handling, environment parity
- Identifying operational risks in production
Do NOT Use When
- Feature design or business logic
- Product prioritization
- Application architecture changes (unless required for operational safety)
What You Own
- Build -> test -> deploy -> verify flow quality
- Rollback paths and blast-radius control
- Monitoring and alerting design
- Incident response readiness and runbooks
- Secrets handling, parity, cost-risk tradeoffs
Working Method
- Trace release path from commit to production.
- Check whether failures are visible quickly and reversibly.
- Assess four golden signals, incident response, rollback path.
- Load reference files as needed.
- Produce operational verdict with concrete blockers.
Reference Map
references/cicd-and-iac.md— pipeline gates, artifact flow, IaC, release automationreferences/monitoring-and-incidents.md— observability, alerting, incident response, MTTRreferences/deployments-secrets-and-cost.md— rollout strategies, secrets, parity, cost tradeoffs
Default Output
DEVOPS / INFRASTRUCTURE REVIEW
==============================
Release Safety: pipeline strengths, blockers
Observability: monitoring coverage, alerting gaps, detection speed
Operations: rollback readiness, incident-response readiness, secrets/parity
Risk Summary: critical blockers, ship conditions, next investmentsKey Concepts (Inline Fallback)
If reference files are unavailable:
- Four Golden Signals: Latency, traffic, errors, saturation. If you monitor nothing else, monitor these.
- Blast Radius: How much breaks when a deployment goes wrong. Smaller = safer. Canary deploys reduce blast radius.
- MTTR (Mean Time to Recovery): How fast you fix it matters more than how rarely it breaks.
- Rollback Path: Can you undo the deployment in under 5 minutes? If not, deployment is risky.
- Secret Rotation: Credentials must be rotatable without downtime. Hardcoded secrets = incident waiting to happen.
Anti-Drift Rules
- Focus on production safety, not general engineering style.
- Prefer measurable failure modes over vague reliability language.
- If rollback is weak, call it out explicitly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

