obs-check

Detect observability gaps in code against OBS-1 through OBS-5 rules.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill obs-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obs-check
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/ccc/skills/obs-check
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill obs-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability is essential for fast incident response and reliable software. OBS-1 through OBS-5 define required practices for logging, tracing, health checks, and actionable error messages. This skill is loaded by the conductor for review, incident response, and new service scaffolding, helping teams detect and fix gaps early.

Core Features & Use Cases

  • Enforces OBS-1 through OBS-5 across codebases to prevent empty catch blocks, unstructured logging, missing trace context, absent health checks, and vague errors.
  • Provides guidance to remediate issues during code reviews, incident response, and scaffolding of new services.
  • Use Case: Teams integrate obs-check into CI or PR review to surface observability gaps and actionable remediation tasks.

Quick Start

Analyze your codebase with obs-check to identify observability gaps and guide remediation.

Frequently Asked Questions about obs-check

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

FAQPage Schema
How do I enforce observability rules for logging and tracing during code reviews?

Enforce observability rules by analyzing codebases to detect empty catch blocks, unstructured logs, missing trace context, absent health checks, and vague error messages, providing specific guidance to remediate these gaps during reviews.

What is the best way to find missing health checks and tracing in my services?

Finding missing health checks and tracing involves scanning services against OBS-1 through OBS-5 rules to identify absent health endpoints and missing trace context, ensuring consistent observability across new and existing services.

How do I prevent empty catch blocks and unstructured logging in my codebase?

Prevent empty catch blocks and unstructured logging by applying observability detection rules that flag these patterns and provide actionable remediation guidance to ensure all caught errors are logged with structured, actionable context.

Can I integrate observability checks into CI pipelines for incident response?

Integrate observability checks into CI pipelines by loading enforcement rules during review workflows and incident response pipelines, surfacing gaps early and generating actionable remediation tasks for consistent logging and health checks.

What observability gaps should I check for when scaffolding new services?

When scaffolding new services, check for empty catch blocks, unstructured logs, missing trace context, absent health endpoints, and vague error messages to satisfy OBS-1 through OBS-5 observability requirements from the start.

Why does my incident response suffer from vague error messages and missing trace context?

Incident response suffers when services lack structured logging, tracing, and health checks because observability gaps prevent fast detection and remediation; enforcing OBS-1 through OBS-5 rules surfaces and fixes these specific issues.