go-observability-reviewer

Name: go-observability-reviewer
Availability: InStock
Author: random6913

Audit Go services for observability gaps across logs, metrics, traces, profiling, and health checks.

1|Updated Mar 23, 2026

Search Tags:#logging #go #observability #prometheus #opentelemetry #pprof #health-checks

Ready to run

npx skills add https://github.com/RaNDoM6913/claude-code-superkit --skill go-observability-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-observability-reviewer
Source: https://github.com/RaNDoM6913/claude-code-superkit/tree/main/packages/codex/skills/go-observability-reviewer
Command: npx skills add https://github.com/RaNDoM6913/claude-code-superkit --skill go-observability-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit Go services for observability completeness across all five signals, ensuring production systems emit logs, metrics, traces, profiling, and health checks for diagnosability.

Core Features & Use Cases

Checks for structured logging with slog and proper context propagation.
Verifies Prometheus metrics registration and sensible histogram buckets.
Validates OpenTelemetry traces and proper span attributes.
Confirms pprof endpoint availability and optional continuous profiling.
Ensures health and readiness endpoints exist and dependencies are probed.

Quick Start

Run the Go observability reviewer against your service to verify all five signals are present and correctly instrumented.

Frequently Asked Questions about go-observability-reviewer

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

FAQPage Schema

How do I audit Go microservices for missing observability signals?▼

Audit Go microservices by checking for structured slog logging, Prometheus metrics registration, OpenTelemetry traces, pprof endpoints, and health probes to identify observability gaps across all five signals.

What does complete Go observability across five signals include?▼

Complete Go observability includes structured logging with slog, Prometheus metric registration, OpenTelemetry context propagation, pprof profiling endpoints, and health or readiness probes for production diagnosability.

How do I verify Prometheus metrics and OpenTelemetry traces in a Go service?▼

Verify Prometheus metrics by checking registration and histogram buckets, and validate OpenTelemetry traces by confirming proper span attributes and context propagation within the Go service.

Does this observability audit check for pprof endpoints and health readiness probes?▼

Yes, the observability audit confirms pprof endpoint availability for profiling and ensures health and readiness endpoints exist while probing dependencies during development and incident investigations.

Can I use this observability review during incident investigations and deployments?▼

Yes, you can run the observability review during development, deployment, and incident investigations to ensure production Go services emit logs, metrics, traces, profiling, and health checks.

Why does my Go service lack proper structured logging and context propagation?▼

A Go service lacks proper observability when structured slog logging and context propagation are missing or incorrectly instrumented, preventing effective diagnosis of production issues.