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
Most recently taken up by
- AloisSeckar/demos-javatheir own version, first seen Nov 9, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- mmurakaru/skillstheir own version, first seen Nov 6, 2026
- kanopi/cms-cultivatortheir own version, first seen Nov 1, 2026
- Hakkadaikon/hymmetheir own version, first seen Oct 26, 2026
- matthull/my-skillstheir own version, first seen Oct 20, 2026
Who's talking about realsenseai/librealsense
- NixOS/nixpkgs“librealsense: add missing support to udev rules”GitHub · Jan 6, 2026 · 2 reactions
- David-Martel/librealsense“fix(fw-update): stop device handles before logger teardown”GitHub · Jul 17, 2026 · 1 reactions
- Bradly187/Personal-Desktop-Agent“chore(deps): bump the python-minor-patch group across 1 directory with 8 updates”GitHub · Nov 2, 2026
- OpenGraphLabs/oglo-python“build(deps-dev): bump the python-dependencies group across 1 directory with 3 updates”GitHub · Nov 1, 2026
- huggingface/lerobot“docs: fix dead Isaac Teleop and RealSense links”GitHub · Oct 30, 2026
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
- Jan 6, 2026librealsense: add missing support to udev rules — NixOS/nixpkgs2 reactions · 7 comments
- Jul 17, 2026fix(fw-update): stop device handles before logger teardown — David-Martel/librealsense1 reaction · 1 comment
- Nov 2, 2026chore(deps): bump the python-minor-patch group across 1 directory with 8 updates — Bradly187/Personal-Desktop-Agent0 reactions
- Nov 1, 2026build(deps-dev): bump the python-dependencies group across 1 directory with 3 updates — OpenGraphLabs/oglo-python0 reactions
- Oct 30, 2026docs: fix dead Isaac Teleop and RealSense links — huggingface/lerobot0 reactions · 1 comment
29 more on GitHub
- Oct 22, 2026build(deps): bump pyrealsense2 from 2.58.4.10922 to 2.59.1.11053 — nvidia-holoscan/holoscan-telesurgery0 reactions
- Oct 20, 2026[D585][GMSL_MUX] Support independent PD 15/30 FPS profiles — polejoe/librealsense0 reactions · 1 comment
- Oct 17, 2026Update pyrealsense2 requirement from >=2.55 to >=2.59.1.11053 — bnrohit/hybrid-rf-scanner0 reactions
- Oct 11, 2026librealsense 2.59.1 — Homebrew/homebrew-core0 reactions · 2 comments
- Oct 4, 2026pyrealsense2: Add version 2.58.4.10922 — riseproject-dev/python-wheels0 reactions · 1 comment
- Sep 23, 2026Add rocm-enabled librealsense package — gbionics/rock-the-conda0 reactions
- Sep 23, 2026Add librealsense — gbionics/rock-the-conda0 reactions · 3 comments
- Sep 14, 2026librealsense: update recipe to latest stable version 2.58.1 — conan-io/conan-center-index0 reactions · 1 comment
- Sep 14, 2026[RSDEV-14616] Use BA10 exclusively for D500 RGB calibration — realsenseai/realsense_mipi_platform_driver0 reactions · 3 comments
- Sep 5, 2026Update pyrealsense2 requirement from >=2.55 to >=2.58.4.10922 — bnrohit/hybrid-rf-scanner0 reactions · 1 comment
- Sep 2, 2026[RSDEV-14097] Expose D585 GMSL gyro sensitivity — realsenseai/realsense_mipi_platform_driver0 reactions
- Aug 31, 2026Package rocm variant of librealsense — conda-forge/librealsense-feedstock0 reactions · 1 comment
- Aug 30, 2026librealsense 2.58.4 — Homebrew/homebrew-core0 reactions · 1 comment
- Aug 28, 2026Fix RVIZ Vizualization of the RealSense D435i Camera Stability and Performance Via ROS Network — arcs-tmu/laika0 reactions
- Aug 15, 2026Update pyrealsense2 requirement from >=2.55 to >=2.58.3.10794 — bnrohit/hybrid-rf-scanner0 reactions · 1 comment
- Aug 5, 2026RSDEV-13232 Integrate D500 stream-group runtime — ghu3/librealsense0 reactions · 4 comments
- Aug 5, 2026Bake ROS 2, RealSense, SiMa CLI, and GitHub tooling into the ARM64 SDK image — sima-vertical-solutions/ros2-sdk0 reactions
- Jul 20, 2026Add python3-pyrealsense2-pip rosdep key to python.yaml — ros/rosdistro0 reactions · 1 comment
- Jul 19, 2026librealsense 2.58.3 — Homebrew/homebrew-core0 reactions · 1 comment
- Jul 9, 2026Support launching Docker GUI apps from Fedora Wayland via XWayland — amoffat/librealsense0 reactions
- Jul 6, 2026Add D401 GMSL dual-RGB support (POC) — ashrafk93/librealsense0 reactions
- Jun 29, 2026chore(deps): bump pyrealsense2 from 2.58.1.10581 to 2.58.2.10647 — AliaksandrNazaruk/janus-camera-stack0 reactions · 1 comment
- Jun 24, 2026Ashraf/zerocopy pr1 — ashrafk93/librealsense0 reactions
- Jun 12, 2026Add placeholder workflow to register build-deb-packages trigger — locusrobotics/librealsense0 reactions
- Mar 11, 2026Add aligned depth topic for RGBD sensor — gazebosim/gz-sim0 reactions · 1 comment
- Feb 17, 2026`pixel_to_real_world` service fails in real mode due to missing `/camera/depth/camera_info` publisher — Final-Project-ROS2/vision0 reactions
- Jan 27, 2026Reliability of the AI-Autostart — A13k5-5/COMP0016_2025_Team11_no-ui-game0 reactions · 1 comment
- Jan 24, 2026[day 1] — z18k/AI-Vision-Learning0 reactions
- Dec 4, 2025[realsense2] update to v2.56.5 — microsoft/vcpkg0 reactions · 2 comments
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.
dversozaSkillpr-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
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 4 projects that use this
SentrySkillcommit
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
GoogleSkillcode-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
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- strands-agents/sdk-python★ 9.2ksame name
- strands-agents/harness-sdk★ 8.9ksame name
- basicmachines-co/basic-memory★ 4.6ksame name
- idaholab/moose★ 2.4ksame name
- AloisSeckar/demos-java★ 25same name
- genlayerlabs/skills★ 19same name
- kanopi/cms-cultivator★ 17same name
- yasunori0418/skills★ 9same name
- BenjaminG/ai-skills★ 4same name
- hartleybrody/.agent-skills★ 4same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-apiSkill
- buildSkill
- cpp-codingSkill
- file-creationSkill
- pr-reviewSkill
- pytest-infraSkill
- testingSkill
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
- Very specific: line 14
Every PR from the RealSense team requires a tracking Jira ticket.
- Very specific: line 17
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 …
- Distinctive: line 18
If you are not sure which ticket is relevant, ask the user before creating the PR.
- Very specific: line 19
Never guess a ticket. Only omit the Tracked on line when the user explicitly says it's OK without one.
- Distinctive: line 23
Every PR description starts with an Overview (1–2 sentences stating the user-visible change), then the body:
- Distinctive: line 44
Keep the Overview jargon-free.
- Very specific: line 47
AI signature: every PR description ends with a 🤖 Generated by AI footer (separated by a --- rule, as shown above).
“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.
Files
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 online 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 AIKeep 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.
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
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.

