ops_prod_monitor

Detect production deployment health issues after code pushes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/maisonnat/axur-tool --skill ops-prod-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops_prod_monitor
Source: https://github.com/maisonnat/axur-tool/tree/main/.agent/skills/ops_prod_monitor
Command: npx skills add https://github.com/maisonnat/axur-tool --skill ops-prod-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production deployment health verification after pushes, ensuring frontend and backend services are reachable and healthy.

Core Features & Use Cases

  • Post-deploy health checks for frontend and backend services.
  • Version reconciliation to ensure deployed code matches the commit.
  • Rollback readiness with safe, tested steps for redeployment.
  • CI/CD integration guidance for automated health validation.

Quick Start

After deployment, run the health checks for frontend and backend and verify the version matches the latest commit.

Frequently Asked Questions about ops_prod_monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run production health checks after a deployment?

Production health checks verify frontend and backend service reachability immediately after a deployment. You run readiness and health endpoint validations post-deploy to confirm the new release is stable and accepting traffic.

What is post-deploy version reconciliation and why does it matter?

Post-deploy version reconciliation ensures the deployed code matches the latest commit. It validates that the active production environment runs the exact version intended, preventing configuration drift and ensuring frontend and backend consistency.

How do I integrate automated health validation into a CI/CD pipeline?

Automated health validation integrates into CI/CD pipelines by enforcing post-release verification steps. The pipeline triggers readiness and health endpoint checks across frontend and backend services automatically after the deployment phase completes.

Can I verify frontend and backend readiness at the same time after a release?

Yes, you can verify frontend and backend readiness simultaneously after a release. The health validation process applies checks across both service types to ensure full stack availability before routing production traffic.

What is the best way to prepare for a rollback if post-deploy health checks fail?

Rollback readiness involves following safe, tested steps for redeployment if health checks fail. The process provides guidance for reverting to the previous stable version while maintaining production environment consistency.