Total 44,141 skills, DevOps & Cloud Services has 2734 skills
Showing 12 of 2734 skills
Prepare and ship a cmux release end-to-end: choose the next version, curate user-facing changelog entries, bump versions, open and monitor a release PR, merge, tag, and verify published artifacts. Use when asked to cut, prepare, publish, or tag a new release.
Adds CI/CD to a .NET project. GitHub Actions vs Azure DevOps detection, workflow templates.
Publishes .NET artifacts from Azure DevOps. NuGet push, containers to ACR, pipeline artifacts.
Composes Azure DevOps YAML pipelines. Templates, variable groups, multi-stage, triggers.
Deploys .NET containers. Kubernetes probes, Docker Compose for local dev, CI/CD integration.
Manage Railway cloud deployments via the Railway CLI. Use when the user wants to deploy, manage services, set variables, view logs, link projects, add databases, configure domains, manage volumes, or perform any Railway platform operation from the terminal.
Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.
Babysit a GitHub pull request after creation by continuously polling CI checks/workflow runs, new review comments, and mergeability state until the PR is ready to merge (or merged/closed). Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and stop only when user help is required (for example CI infrastructure issues, exhausted flaky retries, or ambiguous/blocking situations). Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer
Troubleshoot production issues using backend function logs. Use when investigating app errors, debugging function calls, or diagnosing production problems in Base44 apps.
Tune Kubernetes HPA scale-up/down behavior, topology spread, and resource requests to reduce idle cluster capacity and ensure nodes can drain. This skill should be used when auditing cluster costs on a schedule, analyzing post-incident scaling behavior, or investigating why replicas or nodes do not scale down.
Establishes instrumentation, monitoring, and alerting foundations.