Health-check automation for OpenShift production clusters post-deployment.
Install
mkdir -p .claude/skills/verify-prod-deployment && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14705" && unzip -o skill.zip -d .claude/skills/verify-prod-deployment && rm skill.zipInstalls to .claude/skills/verify-prod-deployment
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when the user says they did a fresh prod deployment and wants to know if everything is okay. Checks pods, deployments, and events on the jotnar-ymir OpenShift cluster.Key capabilities
- →Inspect recent git logs for changes
- →Check the running status of pods in OpenShift
- →Verify deployment rollout status
- →Note updated imagestreams
- →Flag warning severity events in the cluster
How it works
This skill verifies a production deployment by checking git logs, pod statuses, deployment rollouts, imagestream updates, and recent cluster events on the jotnar-ymir OpenShift cluster.
Inputs & outputs
When to use verify-prod-deployment
- →Verifying prod rollout success
- →Debugging deployment pod restarts
- →Auditing OpenShift cluster events
About this skill
Verify Production Deployment
Overview
Check the health of the jotnar-ymir OpenShift cluster after a fresh deployment. Run these commands in order and report findings.
Steps
1. What changed
git log --oneline -25
2. Pod status
oc get pods -n jotnar-ymir--jotnar-ymir
Expected: All agent/service pods Running, completed jobs Completed, zero Error or CrashLoopBackOff or ImagePullBackOff.
3. Deployment rollout status
oc get deploy -n jotnar-ymir--jotnar-ymir
Expected: All deployments show READY count matches desired (e.g. 2/2, 1/1).
4. Imagestreams
oc get imagestream -n jotnar-ymir--jotnar-ymir
Note the UPDATED timestamp for each imagestream. In the report, call out any agent or mcp-server imagestream updated within the last 24 hours — these are the ones that just rolled out.
5. Recent events
oc get events -n jotnar-ymir--jotnar-ymir --sort-by='.lastTimestamp' | tail -40
Look for Warning severity lines — Normal is noise. Flag anything other than routine Pulling/Pulled/Created/Started/Completed.
Reporting
Report as a short table or bullet list:
- All pods running: yes/no
- Any restarts: yes (pod name + count) / no
- Any warnings in events: yes (what) / no
- Deployments all READY: yes/no
- Imagestreams updated <24h: list each (name, tag, updated) — highlight agents and mcp-server
- Overall verdict: OK or ISSUE: <what>
Known gotchas
- Recreate strategy: Deployments use
Recreate(not RollingUpdate). During rollout there is a brief gap with 0 pods — normal, not a failure. - Quota deadlock: If new pods show
FailedCreate+ quota error, checkoc get appliedclusterresourcequotas. Usually resolves itself with Recreate strategy. - jira-issue-fetcher jobs: These are cronjobs that run every 5 minutes and complete quickly —
Completedstatus is expected and healthy.
When not to use it
- →When the deployment is not on the jotnar-ymir OpenShift cluster
- →When the user is not asking about a fresh production deployment
- →When the task is to debug a specific application issue rather than overall deployment health
Limitations
- →Limited to the jotnar-ymir OpenShift cluster.
- →Focuses on overall deployment health, not specific application debugging.
- →Assumes `Recreate` strategy for deployments, allowing brief gaps with 0 pods.
How it compares
This skill provides a standardized, systematic check of multiple OpenShift components to assess overall deployment health, unlike a manual, ad-hoc inspection.
Compared to similar skills
verify-prod-deployment side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| verify-prod-deployment (this skill) | 0 | 1mo | Review | Intermediate |
| ops | 0 | 1mo | Review | Advanced |
| deployment-pipeline-design | 6 | 2mo | Review | Advanced |
| observability-engineer | 12 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ops
denniszielke
>
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
observability-engineer
sickn33
Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.
cloudflare-deploy
davila7
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
mlops-engineer
sickn33
Build comprehensive ML pipelines, experiment tracking, and model registries with MLflow, Kubeflow, and modern MLOps tools. Implements automated training, deployment, and monitoring across cloud platforms. Use PROACTIVELY for ML infrastructure, experiment management, or pipeline automation.
senior-devops
davila7
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.