Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
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.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/rapidsai/cudf --skill review-cudfThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Showing SKILL.md
| name | review-cudf |
| description | Use this skill to review GitHub pull requests for cudf |
Use this skill when the user invokes /review-cudf with:
cudf GitHub repository is located at: https://github.com/rapidsai/cudf
gh pr view <PR_NUMBER> --repo rapidsai/cudf --json title,body,files,additions,deletions,baseRefName,headRefName
gh pr diff <PR_NUMBER> --repo rapidsai/cudf
Hint: Check if GH_TOKEN (or GitHub CLI auth) is already configured in the environment (for example via your secret manager) so gh can authenticate and bypass rate limits; do not run gh auth token from within the agent. If gh auth is unavailable, fall back to GitHub's raw diff/patch URLs, git fetch of the PR ref, unauthenticated GitHub REST API with curl, or any other available methods.
Fetch review comments already posted for context on what's already been suggested and need not be repeated.
Read the Developer Guide (cpp/doxygen/developer_guide/DEVELOPER_GUIDE.md) — it is the authoritative reference for libcudf conventions. All rules in the guide apply during review. The checklist below calls out the most review-relevant rules and adds items not covered by the guide.
Analyze the changes against the checklist below, reading relevant source files as needed for context.
Produce a structured review using the output format at the bottom.
Dump the structured review to .agents/reviews/<PR_NUMBER>/review.md
For the detailed review checklist, read these files:
cpp/REVIEW_GUIDELINES.mdpython/REVIEW_GUIDELINES.mdcpp/doxygen/developer_guide/DEVELOPER_GUIDE.mdcpp/doxygen/developer_guide/TESTING.mdcpp/doxygen/developer_guide/BENCHMARKING.mdcpp/doxygen/developer_guide/DOCUMENTATION.mdUse all applicable checklist items from those files when reviewing the PR. The Developer Guide is the authoritative reference for libcudf conventions — all rules in the guide apply during review.
| Topic | Path |
|---|---|
| Developer guide | cpp/doxygen/developer_guide/DEVELOPER_GUIDE.md |
| Testing guide | cpp/doxygen/developer_guide/TESTING.md |
| Benchmarking guide | cpp/doxygen/developer_guide/BENCHMARKING.md |
| Documentation guide | cpp/doxygen/developer_guide/DOCUMENTATION.md |
| Profiling guide | cpp/doxygen/developer_guide/PROFILING.md |
Online libcudf API docs if needed: https://docs.rapids.ai/api/cudf/nightly/libcudf/
Structure your review as follows:
## PR Review: <PR title>
**PR:** <link>
**Summary:** <1-2 sentence summary of what the PR does>
### Findings
#### Critical
- **[file:line]** Description of issue that must be fixed before merge.
#### Suggestions
- **[file:line]** Description of improvement to consider.
#### Nits
- **[file:line]** Minor style or formatting issue. Keep these minimal, don't suggest adding comments around every line of code or obvious logic.
#### Highlights
- Highlight well-written code, good test coverage, or clever solutions.
### Verdict
One of: **Approve**, **Request Changes**, or **Comment**
With a brief justification.
If there are no findings in a category, omit that category.