codereview-observability

Review code changes for logging, metrics, tracing, and alerting quality.

8|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/xinbenlv/codereview-skills --skill codereview-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codereview-observability
Source: https://github.com/xinbenlv/codereview-skills/tree/main/skills/codereview-observability
Command: npx skills add https://github.com/xinbenlv/codereview-skills --skill codereview-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review often overlooks observability quality, leading to deployment of features that are difficult to monitor, debug, or operate in production.

Core Features & Use Cases

  • Logging Quality: validate logs are actionable and free of secrets.
  • Metrics Coverage: ensure key signals are captured for reliability and performance.
  • Tracing: verify end-to-end traces across distributed services.
  • Alertability: confirm failures produce meaningful alerts and runbooks.
  • Use Case: Review a PR that adds a new logging library; ensure structured logs and correlation IDs are present.

Quick Start

Activate the codereview-observability skill when reviewing a PR that changes logging, metrics, or tracing instrumentation to receive guidance on observability improvements.

Frequently Asked Questions about codereview-observability

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

FAQPage Schema
How do I review logging and tracing quality in a pull request?

To review logging and tracing quality in a pull request, activate this skill during PR review to validate structured logs, verify end-to-end distributed traces, and enforce alertability. It applies a structured checklist to provide actionable code patterns.

What should I check in code to ensure metrics coverage and alertability?

To ensure metrics coverage and alertability in code, check that key reliability signals are captured and failures produce meaningful alerts with runbooks. This skill validates your PR against an observability checklist covering metrics, tracing, and alerting.

How do I validate that new logs are actionable and free of secrets?

Validate that new logs are actionable and free of secrets by reviewing logging quality during code changes. This skill enforces a checklist confirming structured logs and correlation IDs are present without exposing sensitive information.

When do I need to review observability changes in distributed systems?

You need to review observability changes in distributed systems when a PR adds or modifies logging, metrics, tracing, or alerting instrumentation. Reviewing these changes prevents deploying features that are difficult to monitor or debug in production.

Does this observability code review skill require specific dependencies?

No, this observability code review skill does not require specific dependencies or components. It operates as a standalone checklist that provides actionable recommendations and code patterns directly during your pull request review process.