Agent skill · software engineering · jeremylongshore
coderabbit-webhooks-events
Build customer-owned automation around Git-provider events containing CodeRabbit reviews without claiming a separate CodeRabbit webhook contract. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "automate CodeRabbit review events".
Why this skill is useful
Adds specific implementation patterns for validating CodeRabbit webhook signatures and handling events that the AI wouldn't reliably generate on its own.
What it needs
Requires coderabbit installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit Review Event Automation Overview Use the Git provider as event authority for normal PR review automation. Reviewed CodeRabbit docs do not establish a general outgoing CodeRabbit webhook and secret. 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 CodeRabbit uses walkthrough comments, inline comments, reviews, and commands. Customer receivers validate the Git provider signature and delivery. Bot identity, repo, PR, action, and event type require allowlists. Slack or Discord automations are separate product surfaces. 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 provider event, identity evidence, repositories, action, idempotency, and replay window. 2. Verify provider signature over raw body before parsing. 3. Normalize required fields and queue an idempotent event behind a policy gate. 4. Test valid, invalid, replay, wrong-identity, duplicate, and out-of-order fixtures. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coderabbit-webhooks-events