agentleFS
IntelRealSenseIntelRealSense/librealsense/.claude/skills/pr-review/SKILL.md

pr-review

Skill9.1k starsChanged 27 days agoApache-2.0View on GitHub

Reply to human or bot review comments on a librealsense pull request. Use before responding to PR review threads.

195 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 2 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the IntelRealSense/librealsense repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about IntelRealSense/librealsense

The biggest 5 of 81 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 81

Talked about on GitHub, Stack Overflow and Hacker News (81 times).

On GitHub · 48

43 more on GitHub

On Stack Overflow · 30

25 more on Stack Overflow

Used with

Projects with it also use oss-pr, pr-automation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CES-LtdSkill

    oss-pr

    Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.

    Also in 3 projects that use this

  • CES-LtdSkill

    pr-automation

    PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".

    Also in 3 projects that use this

  • jtenniswoodSkill

    expert-reset

    Reimagine this repository from first principles using the current product and user experience as the target. Use when the user says "/expert-reset", asks how the project should be rebuilt if starting again, wants bold architecture or component-structure recommendations, or wants a research-only reset plan unconstrained by current implementation details.

    Also in 3 projects that use this

  • jtenniswoodSkill

    updates

    Summarize user-facing project updates from the last 7 days, ordered by importance and written as one-sentence "Feature: description" entries. Use when the user says "/updates", asks what changed recently, or wants a concise list of recent features, device support, fixes that users will notice, or other product value.

    Also in 3 projects that use this

  • openchamberSkill

    clack-cli-patterns

    Use when creating or modifying OpenChamber CLI commands, prompts, terminal output, non-TTY behavior, `--quiet`, or `--json` behavior.

    Also in 3 projects that use this

  • openchamberSkill

    drag-to-reorder

    Use when implementing or modifying OpenChamber sortable or drag-to-reorder behavior, especially `@dnd-kit`, touch/mobile interactions, variable-width items, or wrapping layouts.

    Also in 3 projects that use this

  • +6 more from openchamber

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    One reply per thread: Don't summarise multiple threads in one comment.

    line 16
  2. Distinctive:

    Don't auto-resolve threads — let the reviewer decide when their concern is settled.

    line 21
  3. Very specific:

    Don't link to PR comments as GitHub issues ("see https://github.com/realsenseai/librealsense/issues/4")

    line 22

“Common” is measured: kept by at least 6 in 10 of the 179 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PR Review Workflow

When to Use This Skill

Replying to review comments (human or bot) on a realsenseai/librealsense pull request.

For opening a PR, pushing commits to one, or updating its description, see the pr-create skill (.claude/skills/pr-create/SKILL.md).

Responding to Review Comments

  • One reply per thread. Don't summarise multiple threads in one comment.
  • Cite the commit SHA that addresses the comment (✅ Fixed in <sha>. <one-line summary>).
  • For deferred items: ⏸ Deferred — <reason>.
  • Be concise. Use short sentences.
  • For disagreements: give a concrete reason (worked example, edge case) before declining.
  • Don't auto-resolve threads — let the reviewer decide when their concern is settled.
  • Don't link to PR comments as GitHub issues ("see https://github.com/realsenseai/librealsense/issues/4")
  • End every comment with a 🤖 Generated by AI line.

Handling Automated Review Bots

BotHow to respond
Aikido (aikido-pr-checks[bot])Fix and reply with commit SHA, or reply @AikidoSec ignore: <reason> if the suggestion is wrong or the pattern is intentional.
rs-agentic-bot (posts as a teammate)Treat as a real reviewer: fix or defer; reply per thread.
Copilot suggestionsApply only if they preserve intent; reply with rationale if declined.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.