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
28 other projects use a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- realsenseai/librealsenseword for word, first seen Nov 16, 2026
- 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
Who's talking about IntelRealSense/librealsense
- A Hacker News story“Best RealSense replacements?”Hacker News · Aug 18, 2021 · 96 points
- realsenseai/librealsense“`librealsense.intel.com` domain no longer resolves — installation instructions in `distribution_linux.md` …”GitHub · Nov 11, 2025 · 20 reactions
- conan-io/conan-center-index“[request] some of most relevant c++ libraries in github (by number of stars)”GitHub · Jan 8, 2020 · 16 reactions
- realsenseai/librealsense“I have written a set of instructions to install librealsense and pyrealsense2 on the Jetson NX”GitHub · Nov 5, 2020 · 15 reactions
- realsenseai/librealsense“ uvcvideo: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024).”GitHub · Nov 22, 2019 · 11 reactions
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
- Nov 11, 2025`librealsense.intel.com` domain no longer resolves — installation instructions in `distribution_linux.md` fail on Ubuntu 22.04 — realsenseai/librealsense20 reactions · 8 comments
- Jan 8, 2020[request] some of most relevant c++ libraries in github (by number of stars) — conan-io/conan-center-index16 reactions · 132 comments
- Nov 5, 2020I have written a set of instructions to install librealsense and pyrealsense2 on the Jetson NX — realsenseai/librealsense15 reactions · 16 comments
- Nov 22, 2019 uvcvideo: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). — realsenseai/librealsense11 reactions · 34 comments
- Nov 30, 2018Installation SDK on the Mac — realsenseai/librealsense11 reactions · 11 comments
43 more on GitHub
- Feb 10, 2020Official support for ROS2 — realsenseai/librealsense8 reactions · 25 comments
- May 26, 2021(Resolved) Apt server is broken/down, gives 403 Forbidden (May 2021) — realsenseai/librealsense7 reactions · 30 comments
- Feb 1, 2020T.265: My experience after about 3 months — realsenseai/librealsense7 reactions · 13 comments
- Jul 18, 2022Announcement: Engineering beta support for Ubuntu 22.04 / ROS2 Humble now available — realsenseai/librealsense6 reactions
- Nov 22, 2018Can not build SDK2.0 from source on MacOS Mojave — realsenseai/librealsense6 reactions · 17 comments
- Aug 25, 2021Prebuilt pyrealsense2 for macOS released — realsenseai/librealsense5 reactions · 8 comments
- Apr 1, 2021Implementation with D435 and T265 INTEL cameras for STEREO-INERTIAL — UZ-SLAMLab/ORB_SLAM35 reactions · 16 comments
- Apr 25, 2019Feature request: HDR mode — realsenseai/librealsense5 reactions · 42 comments
- Apr 8, 20182.10.3 patch-realsense-ubuntu-xenial.sh fails with — realsenseai/librealsense5 reactions · 14 comments
- Apr 4, 2019Get number of frames in bag file using pyrealsense2 — realsenseai/librealsense4 reactions · 12 comments
- Mar 7, 2019Release intel-realsense-dfu for bionic — realsenseai/librealsense4 reactions · 8 comments
- Feb 13, 2018Add RSSDK 2.0 (librealsense2) grabber — PointCloudLibrary/pcl4 reactions · 79 comments
- Jan 16, 2025Document how to use the device on WSL — robotology/yarp-device-realsense23 reactions · 6 comments
- Jan 30, 2023Avoid to call wait_for_frames in the get functions for the RealSense class — gbionics/bipedal-locomotion-framework3 reactions · 3 comments
- Mar 8, 2022Unreal Engine 4.27 support — realsenseai/librealsense3 reactions · 2 comments
- Aug 3, 2020add enable (SetBool) service for disabling/enabling sensor streams — realsenseai/realsense-ros2 reactions · 5 comments
- Jan 8, 2019fix nite2 support, fix intrinsics — realsenseai/librealsense2 reactions · 1 comment
- Nov 24, 2024Patch librealsense v2.44.0 to include `<chrono>` for `system_clock` — isl-org/Open3D1 reaction · 1 comment
- Feb 8, 2023librealsense2: Update to librealsense 2.53.1 — realsenseai/meta-intel-realsense1 reaction
- May 26, 2021Fix librealsense installation in CI — gbionics/bipedal-locomotion-framework1 reaction
- Dec 6, 2020Upgrade librealsense2 to 2.40.0 — bytedeco/javacpp-presets1 reaction
- Sep 19, 2018Add librealsense2 dependency to package.xml — realsenseai/realsense-ros1 reaction · 2 comments
- Jun 8, 2018videoio: update librealsense to API 2.0 — opencv/opencv1 reaction
- Feb 9, 2018Fix illegal RosBag keys by replacing spaces with underscores — realsenseai/librealsense1 reaction · 4 comments
- Oct 30, 2026docs: fix dead Isaac Teleop and RealSense links — huggingface/lerobot0 reactions · 1 comment
- May 31, 2026react-viewer: auto-detect device hot-plug via ctx callback — AviaAv/librealsense0 reactions · 1 comment
- May 20, 2026testing stuff — AviaAv/librealsensesays it tested it0 reactions · 7 comments
- Mar 20, 2026Added throttle of logs — MuLTechnologies/librealsense0 reactions
- Jul 22, 2025Add support to use system provided nlohmann_json library if requested — realsenseai/librealsense0 reactions · 7 comments
- Jul 22, 2025librealsense-gui: 2.56.3 -> 2.57.7 — NixOS/nixpkgs0 reactions · 8 comments
- Jul 9, 2025Improved support to build libraries in shared mode — realsenseai/librealsense0 reactions · 7 comments
- Jan 27, 2025Handle D430GMSL PID for fw update — gwen2018/librealsense0 reactions
- Feb 14, 2024Cant build with message Could NOT find PythonInterp (missing: PYTHON_… — realsenseai/librealsense0 reactions · 3 comments
- Nov 17, 2023Manual acquisitions — secomind/librealsense0 reactions
- Nov 17, 2023implement periodic acquisitions with thread — secomind/librealsense0 reactions
- Jun 17, 2023android-examples-recording-plus — realsenseai/librealsense0 reactions · 3 comments
- Apr 27, 2023Re-use device buffer in yuy2 cuda helper — realsenseai/librealsense0 reactions · 2 comments
- May 16, 2022Dispatcher deadlock workaround — realsenseai/librealsense0 reactions · 8 comments
- Apr 23, 2022PLY vertices data on a single line — realsenseai/librealsense0 reactions · 1 comment
- May 10, 2021Explicitly set OPENSSL_ROOT_DIR in libcurl build — realsenseai/librealsense0 reactions · 3 comments
- Feb 5, 2020Enable linear interpolate of Gyro and Accel data over IMU topic — intel/ros2_intel_realsense0 reactions · 1 comment
- Jan 24, 2020Publish messages using frame timestamp — intel/ros2_intel_realsense0 reactions · 1 comment
- Dec 5, 2019Add Dockerfile for reproducible builds — intel/ros2_intel_realsense0 reactions · 1 comment
On Stack Overflow · 30
- May 15, 2018error: Updating from such a repository can't be done securely, and is therefore disabled by default5 votes · 3 answers
- Nov 6, 2020RGB image captured by Intel realsense camera is dark (using python code)4 votes
- Oct 29, 2019Pointcloud and RGB Image alignment on RealSense ROS4 votes
- Jun 6, 2018Pyrealsense2 (Librealsense SDK 2.0): choose cam from Serial Number3 votes · 1 answer
- Mar 26, 2018Face landmark detection using Intel RealSense Compatiblity SDK3 votes
25 more on Stack Overflow
- Feb 14, 2018Windows Hello API3 votes
- Aug 5, 2020How to align already captured RGB and Depth images2 votes
- Nov 26, 2019Intel RealSense Depth Camera D435i noises and mounds2 votes · 1 answer
- Jan 13, 2019Machine Learning: Question regarding processing of RGBD streams and involved components2 votes
- Aug 22, 2018Error running RealSense D435 on Ubuntu 16.04(4.4.0-131-generic)2 votes
- May 17, 2018intel real sense sdk programming in vs20152 votes
- Jul 25, 2023Depth camera not calibrated when using from pyrealsense1 vote
- Sep 9, 2022Realsense D435 change resolution in MATLAB1 vote
- Oct 28, 2021How to install pyrealsense2 on Mac Os?1 vote
- Jul 9, 2021Realsense D435 change resolution in MATLAB1 vote · 2 answers
- Mar 5, 2021Translate Region of Interest from RGB video to Depth video using OpenCV1 vote
- Oct 6, 2020threshold depth distance in image opencvsharp c# intel realsense1 vote
- Dec 10, 2018RGB image with depth info1 vote
- Jul 5, 2018mapping depth image to color image with realsense2 about opencv1 vote · 2 answers
- Apr 2, 2023Advanced depth visualisation Intel Realsense camera in python0 votes
- Dec 4, 2022Cannot get intelrealsense to compile from source on a Raspi4 8GB0 votes
- Sep 7, 2022On Raspberry Pi 4 with Ubuntu 22.04 don't work ioctl0 votes
- Jun 21, 2022Intel realsense R200: Errors when running 'make'0 votes
- Oct 6, 2021Intel Realsense - unable to read bag file0 votes
- Jun 23, 2021Intel RealSense - Align depth and color in two numpy arrays0 votes
- Oct 8, 2020Display point cloud continuous c# Intel Realsense0 votes · 1 answer
- May 20, 2020Pointer Exception while getting RGB values from (video) frame Intel Realsense0 votes · 2 answers
- Mar 15, 2019Save WriteableBitmap C# WPF video stream to file0 votes
- Dec 12, 2018How to know the orientation angle of real Sense depth Camera?0 votes
- Nov 2, 2016Error while compiling librealsense in clion0 votes
On Hacker News · 3
- Aug 18, 2021Best RealSense replacements?96 points · 82 comments
- Jan 21, 2016RealSense open source library released by Intel for Linux OS X and Windows2 points
- Jan 22, 2016LibrealSense: Cross-platform camera capture from Intel1 point
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 versions28 projects use a version of this.
Word for word · 1
- realsenseai/librealsense★ 9.1k100% same
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.

