code-add-observability

Community

Add a debuggable evidence trail to integrations.

Authorwebdevcody
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill prevents silent integration failures by adding structured, leveled logs and typed error reporting exactly at system boundaries, so later fixes can rely on concrete evidence instead of guessing.

Core Features & Use Cases

  • Integration-boundary instrumentation: Adds logs around outbound HTTP, inbound webhooks/routes, IPC, spawn/exec, env injection, file writes, queues, and hook/MCP calls.
  • Logger discovery & conformity: Detects and conforms to the project’s existing logger; proposes a minimal zero-dependency fallback if none is found (without installing first).
  • Silent-failure protection: Replaces swallow patterns like empty catches and || true-style behavior with logged equivalents while preserving semantics.
  • Discoverability for /fix-bug: Ensures event names are greppable and documents where logs land so a later reactive skill can find the trail quickly.

Quick Start

Tell the AI which feature or integration you want to instrument, then ask it to wire up observability for its boundaries and verify that at least one boundary log event actually fires.

Dependency Matrix

Required Modules

None required

Components

references

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: code-add-observability
Download link: https://github.com/webdevcody/go-mailing-list/archive/main.zip#code-add-observability

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.