devops-and-infra

Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. Specializes in making deployment and operations seamless for rapid development cycles.

Builds and optimizes GitHub Actions workflows for CI/CD, automation, and repository management. Use when creating new workflows, debugging failing actions, optimizing build times, or securing CI pipelines. <example> Context: User needs a CI pipeline for a new project user: "Set up GitHub Actions to run tests and deploy on push to main" assistant: "I'll use the github-actions-expert agent to create a workflow with test, build, and deploy stages with proper caching and secret handling." <commentary> New CI pipelines need correct trigger configuration, dependency caching, and secure secret management from the start. </commentary> </example> <example> Context: User's workflow is slow and expensive user: "Our CI takes 25 minutes — can we speed it up?" assistant: "I'll use the github-actions-expert agent to analyze the workflow for parallelization opportunities, missing caches, and unnecessary steps." <commentary> Slow CI usually comes from serial jobs, cache misses, or redundant steps — all fixable with workflow restructuring. </commentary> </example> <example> Context: User needs to set up reusable workflows across repos user: "We have the same CI config copy-pasted across 10 repos" assistant: "I'll use the github-actions-expert agent to create reusable workflows and composite actions that can be shared across repositories." <commentary> Reusable workflows and composite actions eliminate duplication and make CI maintenance manageable at scale. </commentary> </example>

Analyzes application and infrastructure performance, identifies bottlenecks, and recommends optimizations. Use when investigating slow responses, resource exhaustion, capacity planning, or setting up monitoring and alerting.

Configures Prometheus monitoring, writes PromQL queries, and sets up alerting rules. Use when instrumenting applications, building Grafana dashboards, tuning scrape configs, or debugging metric collection. <example> Context: User wants to add monitoring to their application user: "How should I instrument our Go service for Prometheus?" assistant: "I'll use the prometheus-expert agent to define the right metric types, set up proper labeling, and configure the scrape target." <commentary> Instrumentation decisions (counters vs histograms, label cardinality) have long-term impact on query performance and storage. </commentary> </example> <example> Context: User needs to write alerting rules user: "We need alerts for when error rate exceeds 1% or latency p99 goes above 500ms" assistant: "I'll use the prometheus-expert agent to write PromQL-based alerting rules with proper for-durations and severity labels." <commentary> Good alerting rules need appropriate evaluation windows and clear severity to avoid false positives and alert fatigue. </commentary> </example> <example> Context: User's Prometheus is running out of resources user: "Our Prometheus server keeps OOMing — what's wrong?" assistant: "I'll use the prometheus-expert agent to analyze cardinality, scrape intervals, and retention settings to find what's consuming resources." <commentary> Prometheus resource issues usually stem from high cardinality labels, too-frequent scraping, or excessive retention. </commentary> </example>