Senior Devops
Give your coding agent a structured CI/CD and senior DevOps reference when you design pipelines, deployments, and operational patterns for a solo-built product.
Overview
Senior DevOps is an agent skill most often used in Build integrations (also Ship launch, Operate infra) that supplies CI/CD patterns, practices, and anti-patterns for pipeline-minded solo builders.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill senior-devopsWhat is this skill?
- Reference patterns for CI/CD best-practice implementation with when-to-use scenarios
- Code-organization, performance, scaling, and monitoring considerations for pipeline-heavy repos
- Security practices framed for pipelines: validation, authZ, and data protection
- Explicit anti-patterns section to steer agents away from risky DevOps shortcuts
- Tools-and-resources pointers for choosing supporting stack around automation
Adoption & trust: 806 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are wiring CI/CD or production delivery alone and need senior-level patterns—not generic snippets—so your agent does not invent fragile pipelines.
Who is it for?
Indie builders designing or refactoring GitHub Actions, Docker, or cloud deploy flows who want a consistent DevOps vocabulary for their agent.
Skip if: Teams that only need a single linter fix with no pipeline work, or builders who already have a locked, audited enterprise pipeline and only want ticket-style edits.
When should I use this skill?
You need CI/CD pipeline guidance, DevOps pattern references, or structured trade-offs while designing or changing how your product builds and deploys.
What do I get? / Deliverables
After the skill runs, you get structured pipeline patterns, security and scaling notes, and explicit trade-offs you can translate into real workflow files and runbooks in your repo.
- Pipeline-oriented implementation notes aligned to your stack
- Documented trade-offs and anti-patterns to avoid in automation
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Pipeline design and integration work usually starts while you are still building how the app ships and connects to infra—not only on launch day. CI/CD, build automation, and environment wiring are integration concerns that sit alongside backend and third-party hooks in the Build phase.
Where it fits
Sketch a first GitHub Actions workflow before you connect staging and production environments.
Align release gates and smoke checks with the pipeline patterns before you tag a public launch.
Revisit bottleneck and monitoring guidance when traffic grows and the same pipeline needs tuning.
How it compares
Use as a procedural DevOps playbook in SKILL.md form, not as a hosted CI service or MCP server that executes builds for you.
Common Questions / FAQ
Who is senior-devops for?
Solo and indie developers shipping SaaS, APIs, or CLIs who want their Claude Code, Cursor, or Codex agent to follow senior DevOps framing when discussing or editing CI/CD.
When should I use senior-devops?
Use it during Build when integrating deployment and automation, during Ship when hardening release steps, and during Operate when you revisit scaling and monitoring around the same pipelines.
Is senior-devops safe to install?
Review the Security Audits panel on this Prism page and inspect the skill source in your repo before granting shell or network access in live CI secrets.
SKILL.md
READMESKILL.md - Senior Devops
# Cicd Pipeline Guide ## Overview This reference guide provides comprehensive information for senior devops. ## Patterns and Practices ### Pattern 1: Best Practice Implementation **Description:** Detailed explanation of the pattern. **When to Use:** - Scenario 1 - Scenario 2 - Scenario 3 **Implementation:** ```typescript // Example code implementation export class Example { // Implementation details } ``` **Benefits:** - Benefit 1 - Benefit 2 - Benefit 3 **Trade-offs:** - Consider 1 - Consider 2 - Consider 3 ### Pattern 2: Advanced Technique **Description:** Another important pattern for senior devops. **Implementation:** ```typescript // Advanced example async function advancedExample() { // Code here } ``` ## Guidelines ### Code Organization - Clear structure - Logical separation - Consistent naming - Proper documentation ### Performance Considerations - Optimization strategies - Bottleneck identification - Monitoring approaches - Scaling techniques ### Security Best Practices - Input validation - Authentication - Authorization - Data protection ## Common Patterns ### Pattern A Implementation details and examples. ### Pattern B Implementation details and examples. ### Pattern C Implementation details and examples. ## Anti-Patterns to Avoid ### Anti-Pattern 1 What not to do and why. ### Anti-Pattern 2 What not to do and why. ## Tools and Resources ### Recommended Tools - Tool 1: Purpose - Tool 2: Purpose - Tool 3: Purpose ### Further Reading - Resource 1 - Resource 2 - Resource 3 ## Conclusion Key takeaways for using this reference guide effectively. # Deployment Strategies ## Overview This reference guide provides comprehensive information for senior devops. ## Patterns and Practices ### Pattern 1: Best Practice Implementation **Description:** Detailed explanation of the pattern. **When to Use:** - Scenario 1 - Scenario 2 - Scenario 3 **Implementation:** ```typescript // Example code implementation export class Example { // Implementation details } ``` **Benefits:** - Benefit 1 - Benefit 2 - Benefit 3 **Trade-offs:** - Consider 1 - Consider 2 - Consider 3 ### Pattern 2: Advanced Technique **Description:** Another important pattern for senior devops. **Implementation:** ```typescript // Advanced example async function advancedExample() { // Code here } ``` ## Guidelines ### Code Organization - Clear structure - Logical separation - Consistent naming - Proper documentation ### Performance Considerations - Optimization strategies - Bottleneck identification - Monitoring approaches - Scaling techniques ### Security Best Practices - Input validation - Authentication - Authorization - Data protection ## Common Patterns ### Pattern A Implementation details and examples. ### Pattern B Implementation details and examples. ### Pattern C Implementation details and examples. ## Anti-Patterns to Avoid ### Anti-Pattern 1 What not to do and why. ### Anti-Pattern 2 What not to do and why. ## Tools and Resources ### Recommended Tools - Tool 1: Purpose - Tool 2: Purpose - Tool 3: Purpose ### Further Reading - Resource 1 - Resource 2 - Resource 3 ## Conclusion Key takeaways for using this reference guide effectively. # Infrastructure As Code ## Overview This reference guide provides comprehensive information for senior devops. ## Patterns and Practices ### Pattern 1: Best Practice Implementation **Description:** Detailed explanation of the pattern. **When to Use:** - Scenario 1 - Scenario 2 - Scenario 3 **Implementation:** ```typescript // Example code implementation export class Example { // Implementation details } ``` **Benefits:** - Benefit 1 - Benefit 2 - Benefit 3 **Trade-offs:** - Consider 1 - Consider 2 - Consider 3 ### Pattern 2: Advanced Technique **Description:** Another important pattern for senior devops. **Implementation:** ```typescript // Advanced example async function advancedExample() { // Code here } ``` ## Guidelines ### Code Organization