Menu
List and resolve all unresolved CodeRabbit review conversations from the current PR
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
| name | coderabbit-coderabbit-conversations |
| description | List and resolve all unresolved CodeRabbit review conversations from the current PR |
| version | 1.0.0 |
| license | Apache-2.0 |
| allowed-tools | Bash,Read,edit_file,todo_write |
| metadata | {"command":"gh api graphql","tags":"github pr review coderabbit"} |
List all unresolved CodeRabbit review conversations from the current PR, create a TODO list to address each one, and resolve them all once fixed.
The gh pr view --json reviews,comments approach only returns review-level data and misses individual conversation threads. GitHub's GraphQL API exposes the reviewThreads connection which gives us:
isResolved)isOutdated)resolveReviewThread mutationAll scripts live in scripts/ relative to this skill file. Run them from that directory.
| Script | Purpose |
|---|---|
get-pr-info.sh | Exports PR_NUMBER, PR_TITLE, PR_URL, OWNER, REPO — sourced by the other scripts |
list-threads.sh | Fetches and prints all unresolved CodeRabbit threads for the current PR |
resolve-threads.sh | Resolves all unresolved CodeRabbit threads for the current PR |
Run from the repo root (or any directory — the scripts use gh context):
./scripts/list-threads.sh
This prints every unresolved, non-outdated CodeRabbit thread with its thread ID, file path, line number, and comment body.
If the PR has more than 100 threads the script exits with a warning. In that case, use cursor-based pagination with the
afterparameter in the GraphQL query.
After listing, use todo_write to create one TODO item per conversation thread. Each TODO should include:
Work through the TODOs:
After all fixes are committed, resolve every thread:
./scripts/resolve-threads.sh
gh pr view --json reviews (which misses thread-level data)coderabbitaiafter parameterCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build functional web components, pages, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics. Do NOT use for explanatory diagrams, architecture overviews, diff reviews, or data tables (use visual-explainer instead). Do NOT use for complex multi-component claude.ai artifacts with React state management, routing, or shadcn/ui (use web-artifacts-builder instead).
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Based on SOC occupation classification
