production-readiness

Name: production-readiness
Availability: InStock
Author: kbwen

Automate pre-ship observability checks for error logging, sinks, health checks, and rollback telemetry.

121|29|Updated Apr 12, 2026

Search Tags:#monitoring #rollback #logging #observability #ci-cd #gate #error-reporting

Ready to run

npx skills add https://github.com/KbWen/agentic-os --skill production-readiness-kbwen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: production-readiness
Source: https://github.com/KbWen/agentic-os/tree/main/.agents/skills/production-readiness
Command: npx skills add https://github.com/KbWen/agentic-os --skill production-readiness-kbwen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production-ready apps require errors to surface to production monitoring, not just appear in debug consoles; this skill ensures observability readiness before shipping to reduce silent failures.

Core Features & Use Cases

Observability Checklist: validate error sinks, health checks, and rollback readiness during review and ship.
Log Sink Documentation: document where production errors go and how they are surfaced.
Rollback Telemetry: define how operators detect when rollback is needed and when it succeeds.

Quick Start

Activate the production-readiness checks during the review and ship phases by running the observability verifications and documenting the error sinks and rollback plan.

Frequently Asked Questions about production-readiness

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

FAQPage Schema

How do I validate monitoring and error reporting readiness before shipping to production?▼

Validate production readiness by automating pre-ship observability checks to ensure production errors reach monitoring systems rather than just appearing in debug consoles. This enforces context-rich logs, documented error sinks, and defined rollback telemetry to reduce silent failures.

What is pre-ship observability and why do I need it for code changes?▼

Pre-ship observability is the automated validation of error logging, sinks, health checks, and rollback telemetry during the review and ship phases. You need it to satisfy end-to-end observability requirements and ensure production errors surface to monitoring systems.

How do I document log sinks and define rollback telemetry for a production deployment?▼

Document log sinks by recording where production errors go and how they are surfaced, and define rollback telemetry by specifying how operators detect when a rollback is needed and when it succeeds. These steps are validated during the automated pre-ship review checks.

Can I enforce health checks and rollback plans during the code review phase?▼

Yes, you can enforce health checks and rollback plans during the review and ship phases. The automated checks validate rollback readiness, error sinks, and context-rich logging to guarantee that code changes meet end-to-end observability requirements before deployment.

Does production-readiness work without external monitoring dependencies?▼

Yes, the automated checks operate without external dependencies to validate your observability setup. It ensures your application's error sinks and rollback telemetry are properly configured and documented, preventing silent failures even when specific monitoring tools are not directly integrated.