ring:dev-sre

The ring:dev-sre skill acts as a critical gatekeeper in the development lifecycle, specifically designed to validate observability standards before deployment. Positioned as 'Gate 2' in the development flow, it operates at the task cadence to ensure that developers have correctly implemented essential monitoring and diagnostic patterns. This skill is strictly analytical; it identifies compliance issues, verifies instrumentation coverage, and enforces anti-pattern constraints without performing any code modifications itself.

• Validates structured logging standards (JSON format with timestamp, level, message, service).

• Enforces strict prohibition of forbidden logging patterns like fmt.Println, log.Fatal, or console.log to ensure production-grade output.

• Verifies OpenTelemetry tracing implementation and context propagation for distributed systems.

• Ensures 90%+ instrumentation coverage across supported languages including Go, TypeScript, and Python.

• Checks for the implementation of canonical log event names (e.g., startup_self_probe_passed) required for downstream alerting systems.

• Dispatches findings to the implementation agent for remediation if discrepancies are detected, facilitating a closed-loop validation process.

• Requires unit_id, language, service_type, and implementation files as input for context-aware validation.

• Follows a cache-first protocol to load SRE standards, ensuring consistent enforcement of organizational best practices.

• Max 3 iterations for remediation; auto-escalates to the user if observability requirements remain unfulfilled after re-validation.

• Integrates with the broader Ring ecosystem to maintain consistency across the software delivery value chain.

• Designed for SREs and developers to maintain high reliability and observability standards in API, worker, batch, and CLI services.