agentleFS
realsenseairealsenseai/librealsense/.claude/skills/pr-create/SKILL.md

pr-create

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

Open a librealsense pull request, push commits to it, or update its description - tracking ticket, description format, description audit. Use before creating or updating a PR.

  • Commits and pushes

27 other projects use a version of this.

Trending

Steady talk.about the whole repository

Dec 2025: 1 mentionJan 2026: 3 mentionsFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 3 mentionsJul 2026: 5 mentionsAug 2026: 6 mentionsSep 2026: 6 mentionsOct 2026: 6 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the realsenseai/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 realsenseai/librealsense

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

See all 34

Talked about on GitHub (34 times).

On GitHub · 34

29 more on GitHub

Used with

Projects with it also use pr-feedback, explore and 2 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.
  • dversozaSkill

    pr-feedback

    Address PR review feedback including inline threads, general comments, bot-generated reviews, PR description findings, check run annotations (inline lint/type/security findings shown in the Files changed tab), code scanning alerts, and CI failures. Use when asked to handle, address, resolve, respond to, or work through PR review comments, review feedback, inline findings, or CI check failures. Triggers on requests like "address PR comments", "handle review feedback", "resolve PR reviews", "fix review comments", "go through PR feedback", "check CI failures", "fix the inline findings on the PR".

    Also in 5 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 4 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 5 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every PR from the RealSense team requires a tracking Jira ticket.

    line 14
  2. Very specific:

    If you know the ticket (the user told you, or you opened the ticket yourself this session), add a Tracked on [RSDEV-1234] line right after …

    line 17
  3. Distinctive:

    If you are not sure which ticket is relevant, ask the user before creating the PR.

    line 18
  4. Very specific:

    Never guess a ticket. Only omit the Tracked on line when the user explicitly says it's OK without one.

    line 19
  5. Distinctive:

    Every PR description starts with an Overview (1–2 sentences stating the user-visible change), then the body:

    line 23
  6. Distinctive:

    Keep the Overview jargon-free.

    line 44
  7. Very specific:

    AI signature: every PR description ends with a 🤖 Generated by AI footer (separated by a --- rule, as shown above).

    line 47

“Common” is measured: kept by at least 6 in 10 of the 24 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 Creation & Update Workflow

When to Use This Skill

Opening a PR, pushing new commits to one, or updating its description on realsenseai/librealsense.

Tracking Ticket — Required

Every PR from the RealSense team requires a tracking Jira ticket. External contributors have no Jira access: link the related GitHub issue instead (Fixes #1234), or skip the line if there is none.

For RealSense team PRs:

  • If you know the ticket (the user told you, or you opened the ticket yourself this session), add a Tracked on [RSDEV-1234] line right after the Overview — bare text, no link.
  • If you are not sure which ticket is relevant, ask the user before creating the PR. Tell them each PR requires a ticket, and let them either provide one or explicitly approve creating the PR without it.
  • Never guess a ticket. Only omit the Tracked on line when the user explicitly says it's OK without one.

Description Format

Every PR description starts with an Overview (1–2 sentences stating the user-visible change), then the body:

**Overview:** <1-2 sentences>

Tracked on [RSDEV-1234]

## Why
<bug, regression, or capability gap>

## Summary
- <what changed and why>

## Test plan
- [ ] <unit/pytest entries, marker/context/iteration counts>
- [ ] <manual or CI verification>

---
🤖 Generated by AI

Keep the Overview jargon-free. Put tables (behavior change, latency, benchmarks) in the body, never in the Overview. Be concise when describing changes. Use short sentences. e.g. avoid listing multiple enum literals when describing added enum.

AI signature: every PR description ends with a 🤖 Generated by AI footer (separated by a --- rule, as shown above). Keep it as the last line; re-add it if the description audit rewrites the body.

Before Every Push — Description Audit

Re-read the PR description before git push. If any concrete detail in the description (iteration counts, timeouts, file paths, marker lists, behavior tables, referenced PR numbers) no longer matches what's actually on the branch, update the description in the same push (gh pr edit <num> --body ...).

The description and the diff must stay in sync.

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.