Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Review and triage PR review comments on the current branch — groups threads by file, separates bots from humans, walks through unresolved comments interactively
Install Review PR Comments
$ npx skills add DataDog/datadog-agent --skill review-pr-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DataDog/datadog-agent review-pr-comments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-pr-comments .claude/skills/review-pr-comments && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "review-pr-comments" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/review-pr-comments into .claude/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/review-pr-commentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DataDog/datadog-agent --skill review-pr-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DataDog/datadog-agent review-pr-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/review-pr-comments .agents/skills/review-pr-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-pr-comments" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/review-pr-comments into .agents/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DataDog/datadog-agent --skill review-pr-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DataDog/datadog-agent review-pr-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/review-pr-comments .cursor/skills/review-pr-comments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-pr-comments" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/review-pr-comments into .cursor/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DataDog/datadog-agent.git --path .agents/skills/review-pr-comments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DataDog/datadog-agent --skill review-pr-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DataDog/datadog-agent review-pr-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/review-pr-comments .gemini/skills/review-pr-comments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-pr-comments" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/review-pr-comments into .gemini/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DataDog/datadog-agent review-pr-commentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DataDog/datadog-agent --skill review-pr-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/review-pr-comments .github/skills/review-pr-comments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-pr-comments" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/review-pr-comments into .github/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DataDog/datadog-agent --skill review-pr-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DataDog/datadog-agent review-pr-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/review-pr-comments .opencode/skills/review-pr-comments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-pr-comments" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/review-pr-comments into .opencode/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review-pr-comments- GitHub stars
- 3.8k
- Token cost
- ~1k tokens
- SKILL.md length
- 394 words
- Files
- 1
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review and triage PR review comments on the current branch — groups threads by file, separates bots from humans, walks through unresolved comments interactively
- Works in 7 steps: Identify the PR → Fetch all review data → Organize into threads → …
- Tasks that involve Pull requests
- SKILL.md covers Prerequisites, Workflow and Edge Cases
- Calls gh and git
What it does
Review PR Comments is an agent skill from DataDog/datadog-agent, published by the product's own GitHub organization. Review and triage PR review comments on the current branch — groups threads by file, separates bots from humans, walks through unresolved comments interactively
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: Main repository for Datadog Agent. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Pull requests
Example prompts
- “/review-pr-comments”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 20eff25. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Review PR Comments loads about 1k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 394 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from DataDog/datadog-agent at commit 20eff25, republished under its Apache-2.0 licence (© DataDog). 394 words, ~1,044 tokens.
Download SKILL.mdSave it as
.claude/skills/review-pr-comments/SKILL.md (or your agent's skills folder).- name
- review-pr-comments
- description
- Review and triage PR review comments on the current branch — groups threads by file, separates bots from humans, walks through unresolved comments interactively
- model
- sonnet
Review PR Comments
Fetch, summarize, and interactively triage review comments on the PR for the current git branch.
Prerequisites
ghCLI authenticated with access to the repository- Current branch must have an open PR (not
mainor a release branch likeN.N.x)
Workflow
Step 1: Identify the PR
BRANCH=$(git branch --show-current)Guard: skip if branch is main, master, or matches release pattern ^\d+\.\d+\.x$.
Find the PR:
gh pr list --head "$BRANCH" --json number,title,url,state --limit 5If no PR found, inform the user and stop.
Step 2: Fetch all review data
Run these three gh api calls in parallel:
# Review comments (inline code comments)
gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/comments --paginate \
--jq '.[] | {id, path, line, body, user: .user.login, created_at, in_reply_to_id, diff_hunk}'
# Top-level reviews (approval/request-changes status + body)
gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/reviews --paginate \
--jq '.[] | {id, user: .user.login, state, body}'
# Issue-level comments (general PR discussion, CI bot reports)
gh api repos/{owner}/{repo}/issues/{PR_NUMBER}/comments --paginate \
--jq '.[] | {id, user: .user.login, body, created_at}'Extract {owner} and {repo} from gh repo view --json owner,name.
Step 3: Organize into threads
Group review comments into conversation threads using in_reply_to_id:
- A comment with
in_reply_to_id: nullstarts a new thread - Replies link to their parent thread
For each thread, track:
- File & line from the root comment
- Author of the root comment
- All replies in chronological order
- Resolution status: resolved if the PR author replied last
Step 4: Classify comments
Separate into two groups:
Bot comments (user login ends with [bot] or is a known CI bot):
- Summarize briefly (e.g., "CI quality gates passed", "Regression detector: no regressions")
- Only highlight actionable items (failures, warnings)
Human reviewer comments:
- These get full treatment in Step 5
Show full SKILL.md (193 more words)Show less
Step 5: Present and triage each human comment
For each unresolved human reviewer comment thread:
- Show context: file, line, diff hunk, the comment body
- Read the current file at the referenced location to understand current state
- Summarize the reviewer's concern in one sentence
- Propose a concrete action: code fix, reply text, or explanation
- Ask the user what to do using AskQuestion:
Options:
- "Fix" → Apply the proposed code change
- "Reply" → Post a reply comment on the PR via gh api
- "Reply with custom message" → Ask user for reply text, then post
- "Add TODO" → Add a TODO item to track for later
- "Skip" → Move to next commentFor already-resolved threads (PR author replied last), present them as a summary group:
- Show the comment + your reply, note it's resolved
- Ask if user wants to revisit any
Step 6: Execute chosen actions
Fix: Edit the file, show the diff to the user. Do NOT commit automatically.
Reply: Post via gh API:
gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/comments \
-f body="$REPLY_TEXT" -f in_reply_to=$COMMENT_IDTODO: Use the TodoWrite tool to track it.
Step 7: Summary
After processing all comments, output a summary table:
| # | File | Reviewer | Action Taken |
|---|------|----------|--------------|
| 1 | path/to/file.go:42 | reviewer1 | Fixed |
| 2 | path/to/other.py:10 | reviewer2 | Replied |
| 3 | path/to/build.bzl:5 | reviewer3 | Skipped (already resolved) |Edge Cases
- No unresolved comments: Report "All review comments are resolved" with approval status summary
- PR not found: Suggest the user push the branch or create a PR first
- Outdated diff hunks: Note that the comment may reference old code; read the current file to verify
- Multiple PRs for branch: Use the most recent open one
© DataDog, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/review-pr-comments of DataDog/datadog-agent.
Open the folder on GitHubat commit 20eff25
Compare with similar skills
Review PR Comments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review PR Comments this skillDataDog/datadog-agent | 3.8k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
More from DataDog/datadog-agent
All 35 skills in this repo- Official
Triage CI Failure
DataDog/datadog-agent
Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.
- Official
Elicit
DataDog/datadog-agent
Run a structured discovery session to build an Allium specification through conversation.
- Official
Follow PR
DataDog/datadog-agent
Monitor the current PR's GitLab pipeline to completion, then report success, auto-fix, or investigate a failure.
- Official
Create Epic Recap
DataDog/datadog-agent
A skill your agent uses when an engineer or manager asks to recap, summarize, or post an update on a Jira Epic — a progress update for an in-progress Epic (how far along it is, what's shipped so…
- Official
Explain Lading Config
DataDog/datadog-agent
Explains a lading.yaml config file from the regression test suite, using the lading Rust source as ground truth for field meanings and defaults.
- Official
Distill
DataDog/datadog-agent
Extract an Allium specification from an existing codebase. An agent skill from DataDog/datadog-agent.
Related
Categories
Questions about Review PR Comments
What does Review PR Comments do?
Review and triage PR review comments on the current branch — groups threads by file, separates bots from humans, walks through unresolved comments interactively. Review PR Comments is an agent skill from DataDog/datadog-agent, published by the product's own GitHub organization.
When should I use Review PR Comments?
Review PR Comments fits situations like: tasks that involve Pull requests.
How do I install Review PR Comments in Claude Code?
Run `npx skills add DataDog/datadog-agent --skill review-pr-comments -a claude-code`. Or copy the skill folder (.agents/skills/review-pr-comments in DataDog/datadog-agent) into .claude/skills/review-pr-comments in your project. Claude Code loads it when a task matches its description.
How do I install Review PR Comments in Codex?
Run `npx skills add DataDog/datadog-agent --skill review-pr-comments -a codex`. Or copy the skill folder (.agents/skills/review-pr-comments in DataDog/datadog-agent) into .agents/skills/review-pr-comments in your project. Codex loads it when a task matches its description.
Can I use Review PR Comments in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DataDog/datadog-agent --skill review-pr-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-pr-comments, .gemini/skills/review-pr-comments, .github/skills/review-pr-comments and .opencode/skills/review-pr-comments in your project.
What does Review PR Comments need to run?
Going by SKILL.md and its folder, Review PR Comments needs the command-line tools its instructions call (gh and git).
Does Review PR Comments access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Review PR Comments safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Review PR Comments use?
Review PR Comments is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Review PR Comments use?
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Review PR Comments?
Skills that share tags, products or a category with Review PR Comments: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review PR Comments?
DataDog (a GitHub organization, an official publisher) maintains it in DataDog/datadog-agent, which has 3,757 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 2026.
Source: DataDog/datadog-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.