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 Comment

by 8starlabs in 8starlabs/ui

A skill your agent uses when the user asks to write, draft, summarize, or compose a pull request description or change summary.

MITAuto-check passedDevelopment

Install PR Comment

skills CLI
$ npx skills add 8starlabs/ui --skill pr-comment -a claude-code

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

GitHub CLI
$ gh skill install 8starlabs/ui pr-comment --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/8starlabs/ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-comment .claude/skills/pr-comment && 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-comment
GitHub stars
140
Token cost
~701 tokens
SKILL.md length
361 words
Files
2
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user asks to write, draft, summarize, or compose a pull request description or change summary.

  • Works in 4 steps: Tell the reviewer what changed in… → Explain why the diff exists, especially… → Group the key changes without dumping a… → …
  • The user asks to write
  • SKILL.md covers Output rules, Apply this skill when, Goals and Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

PR Comment is an agent skill from 8starlabs/ui. Use when the user asks to write, draft, summarize, or compose a pull request description or change summary. Covers reviewer-facing PR bodies, strict Summary plus Key Changes formatting, and issue-closing keywords when the linked issue is known.

Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).

It sits in Development, covering Pull requests. It works with shadcn/ui. The repository describes itself as: 8StarLabs UI is a component library designed for developers who want niche, high-utility UI elements that you won’t find in standard libraries. The licence is MIT.

When your agent uses it

  • The user asks to write
  • Compose a pull request description

Example prompts

  • “/pr-comment”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Tell the reviewer what changed in user-visible terms.
  2. Explain why the diff exists, especially the root cause.
  3. Group the key changes without dumping a file-by-file changelog.
  4. Include issue-closing language when there is a linked issue.

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

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

  • Network

    No URLs in SKILL.md.

    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 Comment loads about 701 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 361 words of instructions outside code blocks.

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

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 8starlabs/ui at commit 9633e2f, republished under its MIT licence (© 8starlabs). 361 words, ~701 tokens.

Download SKILL.mdSave it as .claude/skills/pr-comment/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pr-comment
description
Use when the user asks to write, draft, summarize, or compose a pull request description or change summary. Covers reviewer-facing PR bodies, strict Summary plus Key Changes formatting, and issue-closing keywords when the linked issue is known.

PR Comment

This skill writes PR descriptions and change summaries for reviewers. It does not handle inline review replies or generic issue comments.

Output rules

  • Output only one fenced markdown block.
  • Use ## Summary and ## Key Changes.
  • Include issue-closing text like Closes #43 when appropriate and known.
  • Do not add prose before or after the fenced block.
  • Keep the write-up concise and copy-paste ready.

Apply this skill when

  • the user says "write a PR", "draft a PR", "summarize this PR", or "describe this diff"
  • the user wants a reviewer-facing change summary
  • the user shares a diff or changed files and wants a polished PR body

Goals

  1. Tell the reviewer what changed in user-visible terms.
  2. Explain why the diff exists, especially the root cause.
  3. Group the key changes without dumping a file-by-file changelog.
  4. Include issue-closing language when there is a linked issue.

Format

markdown
## Summary

<one short paragraph, usually 2-4 sentences>

## Key Changes

<1-3 bullets for a small change, or grouped bullets by area for a larger one>

Closes #<issue>
## Summary

The summary should cover:

  • what changed
  • where it changed
  • why it changed

Lead with the user-visible surface or workflow. Include the root cause when it helps the reviewer understand why the diff exists.

## Key Changes
  • Small change: use 1-3 bullets total.
  • Multi-area change: group bullets by area with a plain label line such as Registry: or Docs:.
  • Name specific symbols, files, commands, or surfaces only when that increases reviewer understanding.
  • Do not restate the summary or enumerate every touched file.
Show full SKILL.md (135 more words)Show less

Style rules

  • Backticks for file paths, commands, symbols, and config keys.
  • Prefer direct reviewer-facing language.
  • Keep the body tight; cut preamble like "This PR" or "In this change".
  • Use root-cause framing when it clarifies a bug fix.
  • Ground claims in the visible diff or in user-provided context.

Issue-closing rules

  • If the linked issue is known and the change resolves it, include a closing line such as Closes #43.
  • If issue linkage is ambiguous, leave it out unless the user asked for it.
  • Put the closing line at the end of the markdown block.

Ask only if needed

If the user gave a diff but not enough context, ask at most once for:

  • the main user-visible surface affected
  • whether an issue number should be closed

If the user already explained the change well enough, write immediately.

© 8starlabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/pr-comment of 8starlabs/ui.

  • SKILL.md
  • evals/evals.json

Open the folder on GitHubat commit 9633e2f

Compare with similar skills

PR Comment 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 Comment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Comment this skill8starlabs/ui140—~701Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

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

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • 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

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

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

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

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

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

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from 8starlabs/ui

  • 8sl Consume Registry

    8starlabs/ui

    A skill your agent uses when users want to install, integrate, or adapt 8StarLabs UI components in a Next.js plus shadcn project.

    140 GitHub stars~781 tokensUpdated 1 mo ago
    Auto-check passed

  • 8sl Component Ship

    8starlabs/ui

    A skill your agent uses when adding, updating, documenting, or validating an 8StarLabs UI component in this repository.

    140 GitHub stars~824 tokensUpdated 1 mo ago
    Auto-check passed

  • 8sl Pattern Review

    8starlabs/ui

    A skill your agent uses when reviewing, debugging, or cleaning up existing 8StarLabs UI usage.

    140 GitHub stars~711 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about PR Comment

What does PR Comment do?

A skill your agent uses when the user asks to write, draft, summarize, or compose a pull request description or change summary. PR Comment is an agent skill from 8starlabs/ui. Use when the user asks to write, draft, summarize, or compose a pull request description or change summary.

When should I use PR Comment?

PR Comment fits situations like: the user asks to write; compose a pull request description.

How do I install PR Comment in Claude Code?

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

How do I install PR Comment in Codex?

Run `npx skills add 8starlabs/ui --skill pr-comment -a codex`. Or copy the skill folder (skills/pr-comment in 8starlabs/ui) into .agents/skills/pr-comment in your project. Codex loads it when a task matches its description.

Can I use PR Comment 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 8starlabs/ui --skill pr-comment -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-comment, .gemini/skills/pr-comment, .github/skills/pr-comment and .opencode/skills/pr-comment in your project.

What does PR Comment need to run?

SKILL.md names no scripts, command-line tools or credentials: PR Comment is instructions for the agent only.

Does PR Comment access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

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

PR Comment 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 PR Comment use?

About 701 tokens (SKILL.md is roughly 2.8k 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 Comment?

Skills that share tags, products or a category with PR Comment: 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 PR Comment?

8starlabs (a GitHub organization) maintains it in 8starlabs/ui, which has 140 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 5, 2026.

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