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.
Resolve PR review comments by pushing code fixes or replying with explanations.
Install Resolve Comments
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add razorpay/blade --skill resolve-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install razorpay/blade resolve-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/razorpay/blade.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/resolve-comments .claude/skills/resolve-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 "resolve-comments" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/resolve-comments into .claude/skills/resolve-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-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/razorpay/blade/tree/master/.agents/skills/resolve-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 razorpay/blade --skill resolve-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install razorpay/blade resolve-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/resolve-comments .agents/skills/resolve-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 "resolve-comments" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/resolve-comments into .agents/skills/resolve-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-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 razorpay/blade --skill resolve-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install razorpay/blade resolve-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/resolve-comments .cursor/skills/resolve-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 "resolve-comments" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/resolve-comments into .cursor/skills/resolve-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-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/razorpay/blade.git --path .agents/skills/resolve-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 razorpay/blade --skill resolve-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install razorpay/blade resolve-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/resolve-comments .gemini/skills/resolve-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 "resolve-comments" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/resolve-comments into .gemini/skills/resolve-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-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 razorpay/blade resolve-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 razorpay/blade --skill resolve-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/resolve-comments .github/skills/resolve-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 "resolve-comments" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/resolve-comments into .github/skills/resolve-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-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 razorpay/blade --skill resolve-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 razorpay/blade resolve-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/resolve-comments .opencode/skills/resolve-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 "resolve-comments" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/resolve-comments into .opencode/skills/resolve-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-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
resolve-comments- GitHub stars
- 656
- Token cost
- ~647 tokens
- SKILL.md length
- 353 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- MIT
At a glance
Resolve PR review comments by pushing code fixes or replying with explanations.
- Works in 5 steps: Fetch Comment Details → Resolve Each Comment → Making Changes in branch → …
- A PR has review comments that need to be auto-resolved
- SKILL.md covers Arguments and Steps
- Calls git and gh
What it does
Resolve Comments is an agent skill from razorpay/blade. Resolve PR review comments by pushing code fixes or replying with explanations. Use when a PR has review comments that need to be auto-resolved.
Its SKILL.md is about 650 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: Design System that powers Razorpay. The licence is MIT.
When your agent uses it
- A PR has review comments that need to be auto-resolved
- Tasks that involve Pull requests
Example prompts
- “/resolve-comments”
Workflow steps
5 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 332e19f. 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:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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
Resolve Comments loads about 647 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 353 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: warnings
The automated check found patterns that need a careful read before installing.
- WarningContains zero-width charactersSKILL.md:33
*: add the label `Human Help Needed 🧑🏻⟨U+200D⟩💻` to the PR instead of guessing.
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 razorpay/blade at commit 332e19f, republished under its MIT licence (© razorpay). 353 words, ~647 tokens.
Download SKILL.mdSave it as
.claude/skills/resolve-comments/SKILL.md (or your agent's skills folder).- name
- resolve-comments
- description
- Resolve PR review comments by pushing code fixes or replying with explanations. Use when a PR has review comments that need to be auto-resolved.
- disable-model-invocation
- true
Resolve PR Review Comments
Arguments
- PR: Link / Number of the PR to resolve comments on
- COMMENT_URLS: Newline-separated list of comment URLs to resolve
Steps
1. Fetch Comment Details
Use gh CLI to fetch the PR and each comment:
gh pr view {PR_NUMBER} --repo razorpay/blade
gh api repos/razorpay/blade/pulls/comments/{COMMENT_ID}2. Resolve Each Comment
For each comment in COMMENT_URLS, determine the appropriate resolution:
- Code fix required: push a fix commit to the PR branch, reply to the inlined comment (mention
[resolved by agent]) at the end, and mark the inlined comment thread as resolved on GitHub. - Clarification request: reply to the inlined comment with a clear explanation and
[resolved by agent]at the end. - Invalid or irrelevant comment: skip resolving it, reply with why it is invalid or irrelevant, and add
[resolved by agent]at the end.- Go through the rest of the relevant code, commits, PR info, whenever applicable, to determine if the comment is invalid or irrelevant.
- Needs PR author input: add the label
Human Help Needed 🧑🏻💻to the PR instead of guessing.
Handling mismatched changes
- Case 1: Diff has piece of change that doesn't match the title or description of the PR.
- In most cases, its safe to assume that the code was changed but the PR info was not updated to reflect the changes. You can go and update the PR info instead of reverting the change.
Show full SKILL.md (134 more words)Show less
3. Making Changes in branch
- Try not to deviate from the original change the PR was intended for (check PR info, diff, relevant code state in that branch, etc to get context whenever needed).
- Its possible that while working on the change, you find out that the comment is invalid or irrelevant or you don't need to make the change at all. In that case, just reply to the inlined comment with small message and add
[resolved by agent]at the end.
4. Push Fixes
If any code fixes were made:
git add -A && git diff --cached --quiet || (git commit -m "fix: <relevant commit message> [resolved by agent]" && git push)5. Reply to Comments
After resolving, reply to each inlined comment with small message and add [resolved by agent] at the end (if you have not already done so).
- Never post a new comment on the PR. Only reply to the inlined comments.
© razorpay, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. 1 hidden character (zero-width or bidirectional) removed. Raw file
Files
Just SKILL.md in .agents/skills/resolve-comments of razorpay/blade.
Open the folder on GitHubat commit 332e19f
Compare with similar skills
Resolve 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 |
|---|---|---|---|---|---|---|
| Resolve Comments this skillrazorpay/blade | 656 | — | ~647 | Automated safety check: Warn | MIT | |
| 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 | 85k | 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 razorpay/blade
All 16 skills in this repoReview PR
razorpay/blade
Review blade PRs by fetching diff, checking CI status, and getting Storybook URL.
Migrate To Rn
razorpay/blade
Add React Native support (.native.tsx files) to Blade components that currently only have web implementations.
Migrate To Svelte
razorpay/blade
Orchestrate parallel migration of Blade React components to Svelte 5.
UI Code Guidelines
razorpay/blade
Important guidelines for writing frontend UI code. An agent skill from razorpay/blade.
Heal PR
razorpay/blade
Heal a Blade PR by fixing CI failures, missing changesets, and sanity issues.
Check Component Readiness
razorpay/blade
This rule helps in reviewing the component before shipping to make sure all important things are checked
Related
Categories
Questions about Resolve Comments
What does Resolve Comments do?
Resolve PR review comments by pushing code fixes or replying with explanations. Resolve Comments is an agent skill from razorpay/blade. Resolve PR review comments by pushing code fixes or replying with explanations.
When should I use Resolve Comments?
Resolve Comments fits situations like: A PR has review comments that need to be auto-resolved; tasks that involve Pull requests.
How do I install Resolve Comments in Claude Code?
Run `npx skills add razorpay/blade --skill resolve-comments -a claude-code`. Or copy the skill folder (.agents/skills/resolve-comments in razorpay/blade) into .claude/skills/resolve-comments in your project. Claude Code loads it when a task matches its description.
How do I install Resolve Comments in Codex?
Run `npx skills add razorpay/blade --skill resolve-comments -a codex`. Or copy the skill folder (.agents/skills/resolve-comments in razorpay/blade) into .agents/skills/resolve-comments in your project. Codex loads it when a task matches its description.
Can I use Resolve 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 razorpay/blade --skill resolve-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/resolve-comments, .gemini/skills/resolve-comments, .github/skills/resolve-comments and .opencode/skills/resolve-comments in your project.
What does Resolve Comments need to run?
Going by SKILL.md and its folder, Resolve Comments needs the command-line tools its instructions call (git and gh).
Does Resolve Comments access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Resolve Comments safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): contains zero-width characters. Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Resolve Comments use?
Resolve Comments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Resolve Comments use?
About 647 tokens (SKILL.md is roughly 2.6k 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 Resolve Comments?
Skills that share tags, products or a category with Resolve 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, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Resolve Comments?
razorpay (a GitHub organization) maintains it in razorpay/blade, which has 656 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 7, 2026.
Source: razorpay/blade on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.