Agent skill · software engineering · jeremylongshore
coderabbit-core-workflow-b
Tune review signal with current learnings, detected guideline files, path instructions, and measured feedback. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "tune CodeRabbit reviews".
Why this skill is useful
Adds specific configuration patterns and tuning strategies for CodeRabbit that enhance its review capabilities based on team preferences.
What it needs
Requires coderabbit installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit Learnings and Guidelines Overview Improve relevance using supported knowledge layers. Avoid invented configuration keys and judge changes against labeled real findings. 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 Learnings arise from natural-language interaction with review comments. Code guidelines can be detected from files such as CLAUDE.md and AGENTS.md. Path instructions guide review; path filters change scope. Configuration precedence can change the effective result. 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. Sample accepted, rejected, and unresolved findings. 2. Separate organization guidance, repository rules, path instructions, and temporary feedback. 3. Draft one supported measurable tuning change and validate resolved config. 4. Pilot comparable PRs and retain only improvements that preserve risky-path coverage. 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-core-workflow-b