file-creation
Skill9.1k starsChanged 27 days agoApache-2.0View on GitHub
Create new source files in the source tree (not a build directory) with the required copyright header. Use before adding any new file to the repository.
Trending
Steady talk.about the whole repository
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
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-apiSkill
- buildSkill
- cpp-codingSkill
- pr-createSkill
- pr-reviewSkill
- pytest-infraSkill
- testingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
When creating new code files, it is critical to ensure they are placed in the project's source tree and NOT in build or temporary …
- Distinctive: line 13
Before creating a file, always inspect the Current Working Directory (CWD).
- Distinctive: line 22
If you are in a build directory, identify the path to the Source Root.
- Very specific: line 23
Look for .git/, LICENSE, README.md, or the top-level CMakeLists.txt.
- Distinctive: line 27
Ensure the parent directory of the file you intend to create exists in the *Source* location.
- Distinctive: line 30
Use the calculated relative prefix in the file path.
- Distinctive: line 37
Every new source/header file must begin with this exact two-line header:
- Very specific: line 51
Git Ignore Rule: Never create files in folders that are typically git-ignored (like build/).
- Very specific: line 52
Consistency: If you see existing source files being referenced with ../ (e.g.
≈ “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
Safe Source File Generation
When creating new code files, it is critical to ensure they are placed in the project's source tree and NOT in build or temporary directories.
Protocol
1. Diagnose Environment
Before creating a file, always inspect the Current Working Directory (CWD).
Red Flags (Build Directory Indicators):
- Presence of
CMakeCache.txt,CMakeFiles/folder. - Presence of
.sln,.vcxproj, or.o/.objfiles in the root of CWD. - The directory name is
build,out,bin, orDebug/Release. - Presence of
ZERO_CHECK.vcxprojorALL_BUILD.vcxproj.
2. Locate Source Root
If you are in a build directory, identify the path to the Source Root.
- Look for
.git/,LICENSE,README.md, or the top-levelCMakeLists.txt. - Calculate the relative path (e.g.,
../or../../).
3. Verify Target Path
Ensure the parent directory of the file you intend to create exists in the Source location.
4. Execute with Relative Paths
Use the calculated relative prefix in the file path.
- Bad:
"examples/my_example.cpp"(If CWD isbuild/, this pollutes the build artifact folder). - Good:
"../examples/my_example.cpp"(Escapes build dir to reach the actual source tree).
Required Copyright Header
Every new source/header file must begin with this exact two-line header:
// License: Apache 2.0. See LICENSE file in root directory.
// Copyright(c) YEAR RealSense, Inc. All Rights Reserved.Critical rules:
YEARmust be the actual current calendar year -- run(Get-Date).Year(PowerShell) ordate +%Y(bash) to confirm the year if unsure.- Never copy the year from a nearby or template file. Template files may be years old.
- Wrong:
// Copyright(c) 2022 RealSense, Inc. All Rights Reserved.(stale year copied from an existing file) - Right:
// Copyright(c) 2026 RealSense, Inc. All Rights Reserved.(actual current year -- adjust as needed)
Important Tips
- Git Ignore Rule: Never create files in folders that are typically git-ignored (like
build/). - Consistency: If you see existing source files being referenced with
../(e.g.../src/main.cpp), likely you are in a build folder and should follow that pattern for new files.
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.

