cmake-workflow
Skill351 starsChanged 3 months agoApache-2.0View on GitHub
Build and test the libuipc project using CMake. Use when building the project, running cmake configure/build commands, compiling with RelWithDebInfo, running Catch2 tests, or when the user asks how to build or test libuipc.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/cpp-format.mdcCursor rule
- .cursor/rules/self-improvement.mdcCursor rule
- commit-conventionSkill
- commitSkill
- cursor-rulesSkill
- documentSkill
- fix-issueSkill
- fix-prSkill
- formatSkill
- github-prSkill
- gpu-optimizationSkill
- project-structureSkill
- push-tagSkill
- repository-setupSkill
- review-prSkill
- run-testsSkill
- simulation-devSkill
- xmake-workflowSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Run from the repository root and keep generated files in an out-of-source directory.
- Very specific: line 19
Use RelWithDebInfo when debugging requires it.
- Distinctive: line 35
Run a test executable directly for a focused Catch2 filter.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
CMake Workflow for libuipc
Build
Run from the repository root and keep generated files in an out-of-source directory. Reuse the selected toolchain, interpreter and existing build settings. For a Release configuration with the checked-in Ninja preset:
cmake -S . -B build --preset ci-release
cmake --build build --config Release -j8Use RelWithDebInfo when debugging requires it; for single-config generators,
select it at configure time with -DCMAKE_BUILD_TYPE=RelWithDebInfo, and use the
matching build/test configuration. Performance comparisons use Release.
Choose parallelism to fit available memory; NVCC can exhaust memory at high -j.
See the maintained build guide for Python packaging, dependency setup and CMake/XMake parity.
Testing
Tests use Catch2 and are also registered with CTest. The fast CPU gate is:
ctest --test-dir build --build-config Release --label-regex fast --output-on-failure --timeout 900Run a test executable directly for a focused Catch2 filter.
Find the compiled test binary in the build output (under <build>/<configuration>/bin/, for example build/Release/bin/) and execute it:
./path/to/test_executableCatch2 test binaries accept standard flags such as:
--list-tests— list all test cases[tag]— filter by tag"test name"— run a specific test by name
Quick Reference
| Step | Command |
| Configure | cmake -S . -B build --preset ci-release |
| Build | cmake --build build --config Release -j8 |
| Run tests | Execute the test binary directly |
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.