coderabbit-webhooks-events — Claude Code skill: setup and use
coderabbit-webhooks-events is a Claude Code skill for designing Git-provider event automation around CodeRabbit reviews. It checks signatures and tests replay handling.
MIT 1 installs ★ 2,935 updated 2026-10-29
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-webhooks-events -a claude-codeWhat coderabbit-webhooks-events does
The skill treats the Git provider as the source of events for ordinary pull-request review automation. It helps define which provider event, repositories, identities, and actions are trusted, then checks the provider signature against the raw request body before parsing it. The reviewed CodeRabbit docs do not establish a general outgoing webhook contract of their own.
It also guides event normalization and idempotent queuing behind a policy gate. Suggested test fixtures cover valid and invalid signatures, duplicates, replays, wrong identities, and out-of-order delivery. If the current contract is unclear, the workflow stops before mutation and asks for owner resolution.
Current CodeRabbit documentation is needed for contract checks, and live changes require approved access. Webhook secrets need security approval; changes to a live organization also need owner approval. Until approval is explicit, the skill keeps work to local drafts and an evidence plan. A comment that merely mentions @coderabbitai is not proof that the sender is the bot.
What it helps with
- design Git-provider event handling for CodeRabbit reviews
- verify provider signatures before parsing request bodies
- filter events by trusted bot identity and repository
- test duplicate, replayed, and out-of-order deliveries
- prepare an approval and rollback plan for live changes
Example prompts for the agent
- Design an automation that alerts us to a verified CodeRabbit changes-requested review.
- Review this handler and make sure it rejects a forged comment that mentions
@coderabbitai. - Draft an event contract and fixtures for signature, replay, and identity checks.
How to install coderabbit-webhooks-events
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-webhooks-events -a claude-code2Manually: put the files in place
~/.claude/skills/coderabbit-webhooks-events/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/coderabbit-webhooks-events/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-webhooks-events -a codex2Manually: put the files in place
.agents/skills/coderabbit-webhooks-events/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-webhooks-events -a cursor2Manually: put the files in place
.cursor/skills/coderabbit-webhooks-events/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/coderabbit-webhooks-events2Manually: put the files in place
.github/skills/coderabbit-webhooks-events/SKILL.md1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-webhooks-events -a gemini-cli2Platform CLI
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/coderabbit-webhooks-eventsManually: put the files in place
.devin/skills/coderabbit-webhooks-events/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-webhooks-events -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about coderabbit-webhooks-events
How do I install coderabbit-webhooks-events in Claude Code?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-webhooks-events -a claude-code. The skill file is placed at ~/.claude/skills/coderabbit-webhooks-events/SKILL.md.
What does coderabbit-webhooks-events do?
It helps design automation using Git-provider events tied to CodeRabbit reviews, including signature validation, identity checks, and delivery tests.
Does the skill rely on a dedicated CodeRabbit webhook?
No. It uses the Git provider as the event authority and does not assume a general outgoing webhook contract from CodeRabbit.
Source text
SKILL.md · MIT
--- name: coderabbit-webhooks-events description: >- 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". allowed-tools: Read,Glob,Grep,Write,Edit version: 2.0.0 argument-hint: "[target] [evidence-or-scope]" model: inherit effort: high author: Jeremy Longshore <[email protected]> license: MIT compatibility: Requires current CodeRabbit documentation and approved access for any live organization, repository, billing, or API change tags: [saas, coderabbit, events, webhooks, automation] --- # 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. ## Approval Boundaries Require security approval for webhook secrets and owner approval before any live mutation. Keep analysis and drafts local until approval is explicit, and record who approved the action and its scope. ## Output An event contract, trust boundary, validation, fixtures, dead-letter policy, and mutation gate. Include source dates, unknowns, and the exact boundary between observed fact and recommendation. ## Error Handling | Condition | Response | |---|---| | Current contract is unclear or docs disagree | Stop mutation, cite both sources, and request owner resolution. | | Required access or approval is missing | Produce a draft and evidence plan only. | | Validation or pilot behavior differs from expectation | Restore the prior state and retain the failed evidence. | | Output contains secrets or private code | Stop, quarantine the artifact, redact it, and notify the data owner. | ## Examples ### Example 1 Notify on a verified CodeRabbit changes-requested review. ### Example 2 Reject a forged comment that merely mentions `@coderabbitai`. ## Validation - Confirm every claim against the dated sources in `references/official-docs.md`. - Verify the requested scope, owner, approval, happy path, failure path, and rollback. - Re-read the effective configuration or provider state after any approved change. - Report unsupported fields, undocumented endpoints, and unverified assumptions as failures. ## Resources - [Official documentation and contract notes](references/official-docs.md) - Re-check the dated contract before any live operation. - Treat unresolved or changed vendor behavior as a stop condition.
© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace