Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/cpp-patternsAPIs, SaaS and identity

cpp-patterns

⁨Modern C++ patterns and best practices for readable, safe, maintainable C++ code: RAII, ownership, error handling, API design, concurrency basics, and build/tooling hygiene. Use when writing or reviewing C++ (C++20+) code.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/cpp-patterns

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
G09mw12drz…TFaAsWDg==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb827313c…dad248e4
b827313ca271…603ddad248e46 files · ⁦6.4 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/coding/cpp-patterns@21cd568

Use this skill for day-to-day modern C++ (C++20+) with a bias for safety, clarity, and maintainable APIs.

If your primary task is test architecture/debugging, activate cpp-testing alongside this skill.

When to activate

  • Writing new C++ modules/libraries/services
  • Reviewing PRs for ownership, lifetime, and exception safety
  • Refactoring for cleaner interfaces and fewer footguns
  • Introducing RAII, smart pointers, and standard library algorithms

Outcome expectations

  • APIs encode ownership and lifetime intent directly in types.
  • Resource cleanup is deterministic (RAII) and exception-safe.
  • Error behavior is consistent per layer (no mixed ad-hoc strategy).
  • Concurrency code has explicit stop/cancellation and race-checking plan.

Core rules (high signal)

  • Prefer RAII for resource ownership; avoid raw new/delete.
  • Use value types by default; use references/pointers to express optionality and non-ownership.
  • Use std::unique_ptr for exclusive ownership; std::shared_ptr only when shared ownership is required.
  • Prefer standard algorithms over hand-written loops when it improves clarity.
  • Keep APIs small; make invalid states unrepresentable where feasible.
  • Define clear error strategy: exceptions vs std::expected-style returns vs status codes.

  1. Clarify ownership and lifetime boundaries first (handles, buffers, views, async captures).
  2. Design the public API around value semantics and explicit contracts.
  3. Implement with RAII wrappers and Rule-of-Zero defaults.
  4. Add warnings/sanitizers/static analysis early in the build.
  5. Review for footguns (dangling views, iterator invalidation, detached threads).

Quick review checklist

  • Ownership is explicit (who allocates, who frees)
  • No leaks or dangling refs (temporaries, string_view, iterator invalidation)
  • Rule of Zero is used; special members defined only when needed
  • const correctness is consistent
  • No surprising implicit conversions; use explicit
  • Concurrency code has a cancellation/stop strategy
  • Error semantics and exception guarantees are documented

Common anti-patterns to reject

  • Owning raw pointers in public APIs
  • Returning/storing std::string_view tied to temporary storage
  • Detached threads that capture this without a lifetime model
  • Broad catch (...) blocks that hide failure context
  • Exposing mutable shared state without synchronization policy

Resources

Load on demand:

  • references/ownership-raii.md — ownership rules, RAII patterns, smart pointers, lifetime
  • references/core-guidelines.md — distilled C++ Core Guidelines pointers
  • references/api-design.md — interface design, value semantics, error strategy
  • references/concurrency.md — jthread, mutex, atomic, condition_variable, stop_token, race detection
  • references/tooling-build.md — compiler warnings, sanitizers, static analysis, binary inspection (MinGW/objdump, MSVC/dumpbin, Linux tools), CMake hygiene

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd568b827313cSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login