dev-sre

Validate Gate 2 observability for logging, tracing, and instrumentation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665 --skill dev-sre-withmartian-sandbox-darkside
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-sre
Source: https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665/tree/main/dev-team/skills/dev-sre
Command: npx skills add https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665 --skill dev-sre-withmartian-sandbox-darkside

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability is essential for production reliability, and Gate 2 ensures that developers have implemented the required logging, tracing, and instrumentation so that systems can be observed and issues diagnosed quickly.

Core Features & Use Cases

  • Validate structured logging to ensure logs include trace context and are emitted in JSON format.
  • Verify OpenTelemetry tracing instrumentation across handlers, services, and repositories with proper span creation and finalization.
  • Assess instrumentation coverage to meet or exceed the 90% threshold and provide actionable feedback.
  • Check context propagation for outgoing HTTP, gRPC, and queue calls to maintain end-to-end traceability.
  • Provide a clear handoff to the next gate and guidance for fixes when issues are found.

Quick Start

Initiate Gate 2 observability validation by supplying unit_id, language, service_type, implementation_agent, and implementation_files.

Frequently Asked Questions about dev-sre

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

FAQPage Schema
How do I validate OpenTelemetry tracing and structured logging before deployment?▼

Instrumentation coverage is assessed to ensure it meets or exceeds a 90% threshold, verifying that logs are structured, traces propagate, and instrumented coverage meets the required standard before providing actionable feedback.

How do I check context propagation for outgoing HTTP, gRPC, and queue calls?▼

Context propagation for outgoing HTTP, gRPC, and queue calls is checked by verifying that OpenTelemetry traces maintain end-to-end traceability across these protocols, ensuring proper context is passed through all network boundaries.

Can I validate observability for both Go and TypeScript microservices?▼

You can validate observability for Go, TypeScript, and Python across api, worker, batch, cli, or library service types to ensure compliance with structured logging and tracing standards.

What is the best way to ensure my service meets observability compliance standards?▼

Ensure observability compliance by validating that services use JSON logs, implement OpenTelemetry spans, propagate context correctly, and achieve instrumentation coverage above the 90% threshold.

How do I start Gate 2 observability validation for my implementation files?▼

Start Gate 2 observability validation by supplying the unit_id, language, service_type, implementation_agent, and implementation_files to initiate the process and receive guidance for fixes when issues are found.