agentsclimarketplace

Handle coderabbit

Skill mappa-ai/skills/utils-skills/handle-coderabbit

Agent skill for integrating Mappa Conduit SDKs in TypeScript, Python, Go, and Rust. Guides first-time setup with media upload, speaker targeting, webhook-first report flows, and documented Conduit APIs for Claude Code and other agentic coding tools.

Install
npx -y skills add mappa-ai/skills --skill handle-coderabbit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Fetch and address CodeRabbit review comments on a pull request. Use when CodeRabbit has reviewed a PR and left comments to resolve, when the user says "handle coderabbit", "address review comments", or "fix coderabbit feedback".

SKILL.md

2.2 KB, as published. Nobody here has run it

Handle CodeRabbit

Read all CodeRabbit review comments on the current PR, address each one with code changes, validate, and push.

Workflow

1. Identify the PR

If no PR number is given, derive it from the current branch:

gh pr view --json number,url,headRefName

2. Fetch CodeRabbit comments

Pull all review comments left by the CodeRabbit bot:

gh pr view <number> --json reviews,comments
gh api repos/{owner}/{repo}/pulls/<number>/comments --jq '.[] | select(.user.login | startswith("coderabbitai")) | {id, path, line, body}'
gh api repos/{owner}/{repo}/pulls/<number>/reviews --jq '.[] | select(.user.login | startswith("coderabbitai")) | {id, body, state}'

Also check the general PR review body (CodeRabbit posts a summary review with actionable items):

gh api repos/{owner}/{repo}/pulls/<number>/reviews --jq '.[] | select(.user.login | startswith("coderabbitai")) | .body'

3. Triage comments

Group comments by category:

  • Actionable — code changes needed (bugs, style, logic issues, missing tests)
  • Nitpicks — optional, address only if quick
  • Questions/clarifications — may need a reply instead of a code change

Skip comments marked [LGTM] or already resolved.

4. Address each actionable comment

For each comment:

  1. Read the referenced file at the referenced line
  2. Understand what CodeRabbit is asking
  3. Make the minimal change that resolves the issue
  4. Do not refactor surrounding code or gold-plate the fix

5. Validate

bun run typecheck
bun run test

Fix any regressions before continuing.

6. Commit and push

git add <changed files>
git commit -m "fix(review): fix explanation"
git push

7. Reply to addressed comments (optional)

If the user wants to close the loop, reply to each resolved comment:

gh api repos/{owner}/{repo}/pulls/<number>/comments/<comment_id>/replies \
  -f body="Addressed in latest commit."

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.