B
brunoulis/cpp-engineering-guardrails
updated 2026-11-18
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site
- Star count
- 0 ★ · brunoulis/cpp-engineering-guardrails · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-17 · last seen 2026-11-20 · seen 4× · listed by 1 sources
- Score
- score 100 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
brunoulis/cpp-engineering-guardrails;first catalogued 2026-11-17;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# C++ Engineering Guardrails v1.4.0
Excerpted from the repository README (abridged)
An installable agent skill for Claude Code, Codex and Hermes that guides coding agents to write, audit, refactor and migrate C++ with evidence instead of opinions: real builds and tests, explicit ownership and lifetimes, measured performance and honest verification status.
It distills lessons from the sibling skills rust-engineering-guardrails and flutter-engineering-guardrails, adapted to what C++ actually guarantees (and doesn't).
> Español: README.es.md
C++-only tooling. The bundled helpers (cpp-rails-audit, cpp-rails-check and
their runners) build in C++23 mode. Explicit C++17 safety and C++20 concept
fixtures exercise older analyzed code. No Rust, Python, Cargo, pip or shell
audit scripts are shipped. CMake/CTest are build/test infrastructure;
GCC/Clang/MSVC, sanitizers, clang-tidy and abidiff are optional external tools
that are discovered, never assumed.
## What's inside
| Path | Purpose |
| SKILL.md | Lightweight entry point: 14 rails (R0–R13), mode selection, progressive reference routing, severity model and handoff contract |
| modes/ | AUDIT, IMPLEMENT, REFACTOR, DEEP-REFACTOR — staged, verifiable, reversible workflows |
| references/ | Memory/lifetime/UB, types and contracts, state and resource lifecycle, native UI and event loops, cancellation/backpressure, concurrency, templates/concepts, security, API/ABI/FFI, determinism, testing, architecture, data layout, compiler optimization, reviewer protocol |
| profiles/ | general, low-latency, library-sdk, legacy-code, engine, service, native-ui, ffi, prototype — risk hypotheses, not rigid styles |
| policies/ | P0–P3 severities, change-dependent quality gates, expiring suppressions |
| tools/cpp-rails/ | C++23 library + CLIs: heuristic scanner, baseline, triage, include topology, JSON/Markdown reports, CMake/CTest runner, clang-tidy, sanitizers, compiler matrix, template instantiation checks, CSV/TSV benchmark comparison |
| tests/ | C++17 safety examples and positive/negative C++20 template fixtures driven by CTest |
| templates/, examples/ | Report, ADR, refactor plan, finding, reviewer checklist, project profile, FFI contract and ready-to-use prompts |
## The four modes
| Mode | Use it for | What it requires |
| Audit | Debt, defects, quality, security and performance review | Read-only, P0–P3 findings with evidence and confidence, remediation plan |
| Implement | New feature or bug fix | Respect existing contracts, smallest coherent patch, tests |
| Refactor | Improve existing code without changing behavior | Options including leave-as-is, characterization tests, regression checks, rollback |
| Deep-refactor | Architecture, boundaries, ownership or ABI migration | ADR, consumer map, staged migration, compatibility plan, independent reviewer |
Combine a mode with a profile, e.g. "audit with the native-ui profile". Example prompts live in examples/AGENT_PROMPTS.md.
## Safety Intelligence (skill v1.4.0)
Use the safety workflow to map resources and
boundaries, review function effects, inspect
initialization/invalidation and plan
incremental adoption. Templates record current
binary/contract identities and evidence for lifetime, invalidation, initialization,
It distills lessons from the sibling skills rust-engineering-guardrails and flutter-engineering-guardrails, adapted to what C++ actually guarantees (and doesn't).
> Español: README.es.md
C++-only tooling. The bundled helpers (cpp-rails-audit, cpp-rails-check and
their runners) build in C++23 mode. Explicit C++17 safety and C++20 concept
fixtures exercise older analyzed code. No Rust, Python, Cargo, pip or shell
audit scripts are shipped. CMake/CTest are build/test infrastructure;
GCC/Clang/MSVC, sanitizers, clang-tidy and abidiff are optional external tools
that are discovered, never assumed.
## What's inside
| Path | Purpose |
| SKILL.md | Lightweight entry point: 14 rails (R0–R13), mode selection, progressive reference routing, severity model and handoff contract |
| modes/ | AUDIT, IMPLEMENT, REFACTOR, DEEP-REFACTOR — staged, verifiable, reversible workflows |
| references/ | Memory/lifetime/UB, types and contracts, state and resource lifecycle, native UI and event loops, cancellation/backpressure, concurrency, templates/concepts, security, API/ABI/FFI, determinism, testing, architecture, data layout, compiler optimization, reviewer protocol |
| profiles/ | general, low-latency, library-sdk, legacy-code, engine, service, native-ui, ffi, prototype — risk hypotheses, not rigid styles |
| policies/ | P0–P3 severities, change-dependent quality gates, expiring suppressions |
| tools/cpp-rails/ | C++23 library + CLIs: heuristic scanner, baseline, triage, include topology, JSON/Markdown reports, CMake/CTest runner, clang-tidy, sanitizers, compiler matrix, template instantiation checks, CSV/TSV benchmark comparison |
| tests/ | C++17 safety examples and positive/negative C++20 template fixtures driven by CTest |
| templates/, examples/ | Report, ADR, refactor plan, finding, reviewer checklist, project profile, FFI contract and ready-to-use prompts |
## The four modes
| Mode | Use it for | What it requires |
| Audit | Debt, defects, quality, security and performance review | Read-only, P0–P3 findings with evidence and confidence, remediation plan |
| Implement | New feature or bug fix | Respect existing contracts, smallest coherent patch, tests |
| Refactor | Improve existing code without changing behavior | Options including leave-as-is, characterization tests, regression checks, rollback |
| Deep-refactor | Architecture, boundaries, ownership or ABI migration | ADR, consumer map, staged migration, compatibility plan, independent reviewer |
Combine a mode with a profile, e.g. "audit with the native-ui profile". Example prompts live in examples/AGENT_PROMPTS.md.
## Safety Intelligence (skill v1.4.0)
Use the safety workflow to map resources and
boundaries, review function effects, inspect
initialization/invalidation and plan
incremental adoption. Templates record current
binary/contract identities and evidence for lifetime, invalidation, initialization,
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/brunoulis-cpp-engineering-guardrails/)
- Source
- github · https://github.com/brunoulis/cpp-engineering-guardrails
- Browse by field
- Open source
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.