cpp
Skill1 starsChanged 3 days agoMITView on GitHub
Router for every C++ task of the user - looks at the request and the project, then loads the right C++ skills (cpp-project, cpp-class, cpp-style, cpp-comments, cmake-style, libutils, libutils-exception, cpp-tests, coverage, benchmark, ci-cd). Invoke manually with /cpp.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- testdino-hq/google-styleguides-skillstheir own version, first seen Nov 8, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- Mindrally/skillstheir own version, first seen Oct 8, 2026
- mordechai30/cpp_skillstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use kotlin.
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.
margeloSkillkotlin
Design, implement, and review Kotlin and Android APIs. Use when working on .kt files, Kotlin nullability, sealed classes/interfaces, coroutines, Android threading, Java interop, or Kotlin-backed React Native Nitro Module implementations.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- Mindrally/skills★ 275same name
- margelo/react-native-skills★ 172same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- G1Joshi/Agent-Skills★ 15same name
- testdino-hq/google-styleguides-skills★ 15same name
- kimtth/agent-skill-100-lines-or-less★ 2same name
- its-ash/skills★ 0same name
- mordechai30/cpp_skills★ 0same 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 repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- write-like-meSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Do not answer from this file: decide which skills apply, load them with the Skill tool (never the other routers: they are manual-only), …
- Distinctive: line 52
Start the answer with one line: which skills were loaded and why (ex: "Skills : cpp-class, cpp-style, cpp-comments (nouvelle classe dans un …
“Common” is measured: kept by at least 6 in 10 of the 7 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
C++ router
<name> (a skill) = the folder of that skill: ~/.claude/skills/<name> (setup.sh) or ${CLAUDE_SKILL_DIR}/../../*/<name> (plugin of the marketplace).
Request given with /cpp: $ARGUMENTS
Do not answer from this file: decide which skills apply, load them with the Skill tool (never the other routers: they are manual-only), then do the task
following them. The request is the text given with /cpp (or, if empty, the latest request of the user;
if there is none, inspect the project and propose what can be done).
1. Look at the context (quickly, in parallel)
CMakeLists.txt,include/,src/,tests/,cmake/config/exceptions/present? Empty folder = new project.- libutils used?
bash <cpp-class>/scripts/detect_libutils.sh <root>(internal/libutils/std),grep -rl "utils::" src include. - Files the request is about (open them before deciding).
2. Pick the skills (several can apply, load all of them before writing)
| Situation | Skills |
| new project / repository / "setup" | cpp-project (it loads the others it needs) |
| new class, interface, abstract, struct, enum, module, main, architecture | cpp-class (+ cpp-style, cpp-comments) |
| write / edit / refactor / fix C++ code | cpp-style + cpp-comments (+ libutils if the project uses it) |
| comments only | cpp-comments (comments for CMake/shell/other files of the project) |
| review C++ code against the user's style | cpp-style + cpp-comments (+ cmake-style if CMake changed) |
CMakeLists.txt, tests CMake, packaging, CPack, find_package | cmake-style |
| "how to do X", which class/function, links/includes of libutils, what's new in libutils | libutils |
| throw/catch/print errors, new error codes, exception JSON, generated exception header | libutils-exception (+ libutils) |
| install / update / remove libutils, build fails because libutils is missing or too old | libutils-install |
| add libutils to the current project (CMake, custom exceptions setup) | libutils-setup |
| unit tests: setup, write tests for a module / the whole project | cpp-tests |
| coverage: measure, what is not tested, fill it, coverage report | coverage (+ cpp-tests) |
| slow code, profiling, benchmark, optimization | benchmark |
| CI / CD workflows (build, tests, xstyle, packages, release) | ci-cd |
| bugs, UB, crashes, memory errors, sanitizers, correctness review | audit-bugs |
| security audit, flaws, exploits, memory errors fixed in passes until clean | audit-security |
| cleanliness / conventions audit, report of the project quality | audit-quality (delivered through report, format asked) |
new .cpp added | also cmake-style (registration in SRC, cpp-class/scripts/cmake_add.py) |
| commit / docs asked at the end | git-conventions / readme-style, html-doc |
Rules: architecture skills never write function logic (cpp-class); when unsure between two rows, load both;
when the project doesn't use libutils, don't load libutils* and use standard C++ (cpp-style std mode).
3. Say it
Start the answer with one line: which skills were loaded and why (ex: "Skills : cpp-class, cpp-style, cpp-comments (nouvelle classe dans un projet libutils)").
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.

