New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

PR Comments

by synnaxlabs in synnaxlabs/synnax

Workflow for working through unresolved review comments on a pull request you authored.

Custom licenceAuto-check passedDevelopment

Install PR Comments

skills CLI
$ npx skills add synnaxlabs/synnax --skill pr-comments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install synnaxlabs/synnax pr-comments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/synnaxlabs/synnax.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pr-comments .claude/skills/pr-comments && rm -rf skills-src

Use ~/.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/

Facts

Skill name
pr-comments
GitHub stars
128
Token cost
~1.5k tokens
SKILL.md length
700 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Custom licence

At a glance

Workflow for working through unresolved review comments on a pull request you authored.

  • Works in 4 steps: Find the comments that need action → Surface what cannot be looped → The loop, one comment at a time → …
  • Asked to address
  • SKILL.md covers Step 1: Find the comments that…, Step 2: Surface what cannot be…, Step 3: The loop, one comment… and Step 4: Land the work, then…, plus 2 more sections
  • Calls gh and jq

What it does

PR Comments is an agent skill from synnaxlabs/synnax. Workflow for working through unresolved review comments on a pull request you authored. Use when asked to address, triage, or work through PR review comments, reviewer feedback, or bot comments. Finds unresolved threads whose last word belongs to the reviewer, researches each one, and brings a recommendation per comment. The user chooses implement, skip, or respond. GitHub writes batch to the end.

Its SKILL.md is about 1.5k 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. It works with GitHub. The repository describes itself as: The data and operations foundation for hardware.

When your agent uses it

  • Asked to address
  • Work through PR review comments
  • Reviewer feedback

Example prompts

  • “/pr-comments”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Find the comments that need action
  2. Surface what cannot be looped
  3. The loop, one comment at a time
  4. Land the work, then write to GitHub

What it can do on your machine

Read from SKILL.md and the folder at commit fdfe2bb. 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:

    • gh
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use 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

PR Comments loads about 1.5k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 700 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 700 words (~1,519 tokens).

“Working through review comments on the user's own PR, one at a time. Every comment is researched before it gets a verdict, because reviewers and bots are each sometimes wrong. The user decides implement, skip, or respond on every one…”

— opening of SKILL.md by synnaxlabs, Custom licence
name
pr-comments

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/pr-comments of synnaxlabs/synnax.

Open the folder on GitHubat commit fdfe2bb

Compare with similar skills

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.

PR Comments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Comments this skillsynnaxlabs/synnax128—~1.5kAutomated safety check: PassCustom licence
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

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.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • 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.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from synnaxlabs/synnax

All 10 skills in this repo

  • Synnax Integration Debug

    synnaxlabs/synnax

    Triage failures from the Synnax integration test suite (uv run tc ...).

    128 GitHub stars~2.1k tokensUpdated today
    Auto-check: notes

  • Console Testing

    synnaxlabs/synnax

    Rules for writing and editing unit tests in the Console (console/src//.spec.ts[x]).

    128 GitHub stars~5.4k tokensUpdated today
    Auto-check passed

  • Code Review

    synnaxlabs/synnax

    Process and hard rules for conducting code reviews in this repo: PRs, branches, commit ranges, and working diffs.

    128 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Create Linear Issue

    synnaxlabs/synnax

    Synnax Linear issue conventions. An agent skill from synnaxlabs/synnax.

    128 GitHub stars~846 tokensUpdated today
    Auto-check passed

  • Design

    synnaxlabs/synnax

    Process and hard rules for designing and planning complex new features, refactors, and re-architectures.

    128 GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • Eb Review

    synnaxlabs/synnax

    Process and hard rules for a fast software quality audit of work this session just produced, or of a solution being proposed before it is built.

    128 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about PR Comments

What does PR Comments do?

Workflow for working through unresolved review comments on a pull request you authored. PR Comments is an agent skill from synnaxlabs/synnax. Workflow for working through unresolved review comments on a pull request you authored.

When should I use PR Comments?

PR Comments fits situations like: asked to address; work through PR review comments; reviewer feedback.

How do I install PR Comments in Claude Code?

Run `npx skills add synnaxlabs/synnax --skill pr-comments -a claude-code`. Or copy the skill folder (.claude/skills/pr-comments in synnaxlabs/synnax) into .claude/skills/pr-comments in your project. Claude Code loads it when a task matches its description.

How do I install PR Comments in Codex?

Run `npx skills add synnaxlabs/synnax --skill pr-comments -a codex`. Or copy the skill folder (.claude/skills/pr-comments in synnaxlabs/synnax) into .agents/skills/pr-comments in your project. Codex loads it when a task matches its description.

Can I use 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 synnaxlabs/synnax --skill 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/pr-comments, .gemini/skills/pr-comments, .github/skills/pr-comments and .opencode/skills/pr-comments in your project.

What does PR Comments need to run?

Going by SKILL.md and its folder, PR Comments needs the command-line tools its instructions call (gh and jq).

Does PR Comments access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is 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 PR Comments use?

PR Comments has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does PR Comments use?

About 1.5k tokens (SKILL.md is roughly 6.1k 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 PR Comments?

Skills that share tags, products or a category with PR Comments: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Comments?

synnaxlabs (a GitHub organization) maintains it in synnaxlabs/synnax, which has 128 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 8, 2026.

Source: synnaxlabs/synnax on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.