add-api
Skill9.1k starsChanged 27 days agoApache-2.0View on GitHub
Add new public API to the librealsense SDK (C/C++ headers, Windows exports, Python bindings, examples) without breaking existing API. Use before adding any function, struct, enum, option or metadata field to include/librealsense2.
1 other project uses a version of this.
Trending
Steady talk.about the whole repository
Most recently taken up by
- glowingkitty/OpenMatestheir own version, first seen Oct 8, 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
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- glowingkitty/OpenMates★ 53same name
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
- buildSkill
- cpp-codingSkill
- file-creationSkill
- pr-createSkill
- pr-reviewSkill
- pytest-infraSkill
- testingSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 1 is distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Add, don't change: Never remove or change the signature, struct layout or enum values of existing public API without explicit user approval …
- Very specific: line 11
Enums: add new values just before the *_COUNT entry.
- Very specific: line 12
Add only what was asked. No summary/design files.
- Very specific: line 26
Use HANDLE_EXCEPTIONS_AND_RETURN(<default>, <args>...) when the function takes arguments, and VALIDATE_NOT_NULL / VALIDATE_RANGE for inputs.
- Very specific: line 28
C++ wrapper: add the method/class in include/librealsense2/hpp/rs_*.hpp, calling the C function and error::handle(e).
- Very specific: line 35
Add the value in the header before *_COUNT (e.g.
- Very specific: line 36
Add its string in src/to-string.cpp (CASE( NAME ) in the matching *_to_string switch).
- Very specific: line 43
Every new C function is in src/realsense.def.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Adding New API to librealsense
Rules
- Add, don't change. Never remove or change the signature, struct layout or enum values of existing public API without explicit user approval — the C API keeps ABI compatibility within a major version.
- Enums: add new values just before the
*_COUNTentry; never renumber existing ones. - Add only what was asked. No summary/design files; use an example instead of a doc unless one is really needed (
doc/<feature>.md). - New files get the copyright header with the current year (see the
file-creationskill).
Checklist — new C function
- Declare in the matching C header
include/librealsense2/h/rs_*.h, with a doc comment and a trailingrs2_error** errorparameter. - Implement in
src/rs.cppusing the API-call wrappers, which turn exceptions intors2_error:
Users2_processing_block* rs2_create_mjpeg_decoder(rs2_error** error) BEGIN_API_CALL { return new rs2_processing_block{ std::make_shared<mjpeg_converter>(RS2_FORMAT_RGB8) }; } NOARGS_HANDLE_EXCEPTIONS_AND_RETURN(nullptr)HANDLE_EXCEPTIONS_AND_RETURN(<default>, <args>...)when the function takes arguments, andVALIDATE_NOT_NULL/VALIDATE_RANGEfor inputs. - Export the symbol in
src/realsense.defnext to related functions. Windows exports only what is listed there — a missing entry builds fine but fails to link for users. - C++ wrapper: add the method/class in
include/librealsense2/hpp/rs_*.hpp, calling the C function anderror::handle(e). - Python: bind it in the matching
wrappers/python/pyrs_*.cpp(e.g.pyrs_processing.cpp,pyrs_device.cpp,pyrs_sensor.cpp,pyrs_frame.cpp) with snake_case names and a docstring. - Example / test: a short C++ example in
examples/<feature>/(withCMakeLists.txt) when the feature is user-facing, and/or a pytest test (see thepytest-infraskill). - Build the library and
pyrealsense2, and try the new API from Python.
Checklist — new enum value (option, metadata, stream, format...)
- Add the value in the header before
*_COUNT(e.g.RS2_OPTION_*inrs_option.h,RS2_FRAME_METADATA_*inrs_frame.h). - Add its string in
src/to-string.cpp(CASE( NAME )in the matching*_to_stringswitch). - Implement it where it applies (e.g. the device/sensor option registration under
src/ds/..., or the metadata parser). - A new enum type also needs
src/core/enum-helpers.h, itsrs2_<type>_to_stringdeclared, exported insrc/realsense.def, and a Python binding inwrappers/python/c_files.cpp.
Before Finishing
git diffshows no changed signatures, struct layouts or enum values ininclude/librealsense2/.- Every new C function is in
src/realsense.def. - Library and Python bindings build; the new API was exercised.
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.

