Agent skill · data analytics · jeremylongshore
coderabbit-observability
Measure review adoption, latency, findings, usage, and outcomes from documented dashboards, exports, reports, or API data. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "measure CodeRabbit reviews".
Why this skill is useful
Adds specific executable scripts for monitoring CodeRabbit review metrics that aren't widely known.
What it needs
Requires gh installed locally. Requires coderabbit account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit Observability Overview Use documented metric definitions and preserve denominators. Avoid scraping bot comments as a substitute for authoritative reporting. Prerequisites Identify the CodeRabbit organization, Git provider, repository, plan, and accountable owner. Read references/official-docs.md and re-check any time-sensitive contract before execution. Use synthetic or read-only evidence until the approval boundary is satisfied. Preserve the repository's independent CI, security, and human-review requirements. Current Contract Git-platform and IDE or CLI metrics have separate definitions. The Usage dashboard explains events, limits, and the Review Log. Data export supports offline analysis. Authenticated metrics APIs depend on plan and permissions. Authentication Treat Git-provider sessions, CodeRabbit web sessions, CLI credentials, and CodeRabbit API keys as separate credentials. Use only an already-approved session or secret-manager reference, never print a secret, and do not place credentials in .coderabbit.yaml, source files, logs, or deliverables. Instructions 1. Define decision, population, provider, repositories, UTC window, and metrics. 2. Export with timestamps, filters, pagination, and exclusions. 3. Compute coverage, response, resolution, and usage with denominators. 4. Compare cohorts and publish thresholds only after baseline evidence. Tool Discipline Use Glob to locate candidate configuration and evidence files without widening scope. Use Grep to find relevant fields, commands, identifiers, and stale claims. Use Read to inspect the smallest required files and authoritative evidence. Use Write only for a new approved local draft or evidence artifact. Use Edit only for a bounded approved change whose rollback is known. Do not use these file tools as a substitute for authenticated CodeRabbit or provider operations. Approval Boundaries Require data-owner approval before user-level exports, scheduled reports, or API credentials. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coderabbit-observability