Monitor CI/CD and Incidents
Developer & Ops
Pipeline
Monitor
Respond
Set up CI/CD monitoring, health checks, and alerting so you know when something breaks before your users do. The idea is to connect your pipelines to your monitoring and have a clear playbook when things go wrong.
Useful for
- You find out about broken builds when someone complains on Slack
- You run production services but have no automated health checks or alerts
- You want to catch deployment failures and performance drops before they snowball
Suggested Skills
Pick skills from the phases below based on what you need. Each phase has an example prompt you can copy and try with your agent.
Pipeline skills manage CI/CD workflows and catch build failures. Monitor skills watch production health, track errors, and check service status. Alert skills notify you when something needs attention.
Pipeline
Set up and manage CI/CD workflows.
try in your OpenClaw assistant
Create a GitHub Actions pipeline for my project that runs tests on every push and deploys to production when I merge to main.
First review and use these skills:
https://clawskills.sh/skills/gitgoodordietrying-cicd-pipeline
Monitor
Watch service health and catch failures.
try in your OpenClaw assistant
Set up health checks for my production API that monitor response times, error rates, and container status.
Respond
Diagnose issues and fix failures quickly.
try in your OpenClaw assistant
My CI build just failed. Diagnose what went wrong, suggest a fix, and re-run the pipeline.