comments · bridglabs — Claude Code skill for pull request reviews
comments is a Claude Code skill that processes feedback on the open pull request for the checked-out branch. It applies valid fixes, pushes commits, and responds to review threads.
no license ★ 104 updated 2026-11-17
npx skills add BridgLabs/opencodereview --skill comments -a claude-codeWhat comments does
The skill gathers review threads and standalone comments on the open pull request tied to the current local branch. It reads each comment in full, checks the referenced code, then sorts feedback into actionable fixes, false positives, skips, questions, or external issues.
For actionable feedback, it makes a focused change, runs checks for the affected area, and creates a separate commit. After pushing, it replies with commit links and resolves only review threads whose fixes were applied. It never force-pushes. The workflow stops if the branch has no matching open PR or the worktree contains unrelated changes.
git and GitHub CLI gh are required. Before starting, the skill reads AGENTS.md and .agents/skills/git/SKILL.md. It works against the checked-out branch’s PR; a PR number, URL, or branch override cannot be supplied.
What it helps with
- collect feedback from review threads and standalone PR comments
- sort actionable findings from false positives and open questions
- commit focused fixes and link them back to review comments
- resolve review threads only after their fixes are pushed
Example prompts for the agent
- Review feedback on the current branch’s PR and apply actionable fixes.
- Sort the PR comments, commit valid changes, and reply with commit links.
- Check the current PR feedback and resolve threads whose issues are fixed.
How to install comments
1Skills CLI (Vercel)
npx skills add BridgLabs/opencodereview --skill comments -a claude-code2Manually: put the files in place
~/.claude/skills/comments/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/comments/
1Skills CLI (Vercel)
npx skills add BridgLabs/opencodereview --skill comments -a codex2Manually: put the files in place
.agents/skills/comments/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add BridgLabs/opencodereview --skill comments -a cursor2Manually: put the files in place
.cursor/skills/comments/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install BridgLabs/opencodereview .agents/skills/comments2Manually: put the files in place
.github/skills/comments/SKILL.md1Skills CLI (Vercel)
npx skills add BridgLabs/opencodereview --skill comments -a gemini-cli2Platform CLI
gemini skills install https://github.com/BridgLabs/opencodereview --path .agents/skills/commentsManually: put the files in place
.devin/skills/comments/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about comments
How do I install comments in Claude Code?
Run npx skills add BridgLabs/opencodereview --skill comments -a claude-code. The skill file is available at ~/.claude/skills/comments/SKILL.md.
What does comments do?
It reviews feedback on the current branch’s open PR, makes suitable fixes in focused commits, pushes them, and replies with commit links. Only fixed review threads are resolved.
What does comments need to run?
It needs git, GitHub CLI gh, and the repository files AGENTS.md and .agents/skills/git/SKILL.md.
Similar skills
All skills for Git and GitHub →comments by other authors comes first.