Skip to content
Skills Library
Programming · Analysis

coderabbit-core-workflow-b

/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".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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".

Triggers from the description

tune CodeRabbit reviews

Arguments

/coderabbit-core-workflow-b [target] [evidence-or-scope]
Original author description

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".

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 83 lines, 519 words
SKILL.md preview
---
name: coderabbit-core-workflow-b
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
version: 2.0.0
argument-hint: "[target] [evidence-or-scope]"
model: inherit
effort: high
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
compatibility: Requires current CodeRabbit documentation and approved access for any live organization, repository, billing, or API change
tags: [saas, coderabbit, learnings, guidelines, review-quality]
---
# 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.

## Approval Boundaries

Require owner approval before changing shared learnings, global overrides, or exclusions. Keep analysis and drafts local until approval is explicit, and record who approved the action and its scope.

## Output

A labeled sample, hypothesis, supported change, comparison metrics, and rollback decision. 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

Move a durable convention into `AGENTS.md` and verify detection.

### Example 2

Replace unsupported `custom_patterns` with documented path instructions.

## 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.
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 1 KB

Versions

RepositoryScoreLicence
This page · jeremylongshore/tons-of-skills-marketplace100MIT
HelixDevelopment/agent100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version d2b3578d3f5d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100coderabbit-performance-tuning
    Improve review speed and signal using measured scope, config, cache, and review behavior without timing bands. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "tune CodeRabbit performance".
  • 100coderabbit-core-workflow-a
    Run the primary CodeRabbit review loop from eligibility through finding disposition and verification. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "run a CodeRabbit PR review".
  • 100coderabbit-core-workflow-a
    Execute CodeRabbit primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "coderabbit main workflow", "primary task with coderabbit".
  • 90coderabbit
    Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.
  • 100coderabbit-config
    Create, update, or validate CodeRabbit repository configuration through the official CLI. Use for .coderabbit.yaml or .coderabbit.yml setup, review-style changes, path guidance, and configuration validation requests.
  • 96coderabbit-review
    Use when you need to evaluate CodeRabbit PR comments and fix or reply

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.