dev-sre

Validate logging, tracing, and OpenTelemetry instrumentation coverage in services.

205|26|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/LerianStudio/ring --skill dev-sre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-sre
Source: https://github.com/LerianStudio/ring/tree/main/dev-team/skills/dev-sre
Command: npx skills add https://github.com/LerianStudio/ring --skill dev-sre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate 2 of the development cycle. This Skill VALIDATES that observability was correctly implemented by developers. It does NOT implement observability code - only validates it.

Core Features & Use Cases

  • Observability validation: ensures logging, tracing, and metrics are present and coherent.
  • Trace correlation check: verifies that distributed traces propagate across services.
  • Instrumentation coverage check: confirms code paths are instrumented according to policy.
  • Usage example: given Gate 0 artifacts with logs and traces, validate end-to-end observability readiness.

Quick Start

Provide Gate 0 implementation artifacts (files and traces) and run the observability validation for the given unit/subtask.

Frequently Asked Questions about dev-sre

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

FAQPage Schema
How do I validate observability implementations across distributed services?

Observability validation checks that logging, tracing, and instrumentation are correctly implemented across services. Provide Gate 0 artifacts with logs and traces, then run validation to verify structured logging, trace correlation, OpenTelemetry instrumentation, and 90%+ coverage across API, worker, batch, CLI, and library services.

What does trace correlation validation check?

Trace correlation validation verifies that distributed traces propagate correctly across services and external dependencies. It ensures end-to-end context propagation so you can follow a request through the entire call chain.

Can I validate observability for different service types?

Yes. Observability validation applies to API services, worker services, batch jobs, CLI tools, and libraries. It checks instrumentation coverage and trace propagation across all these service types during Gate 2 validation.

What does instrumentation coverage validation measure?

Instrumentation coverage validation confirms code paths are instrumented according to policy and reports coverage percentages. It ensures your services meet the 90%+ instrumentation coverage requirement for Gate 2 handoffs.

How is observability validation different from implementing observability?

Observability validation audits existing logging, tracing, and instrumentation to ensure they work correctly. It does not implement observability code—it only verifies developers implemented it properly and provides standardized reporting for Gate handoffs.