Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
aeondave/cpp-patternsAPIs, SaaS e identidad

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 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 10 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

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

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
G09mw12drz…TFaAsWDg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paqueteb827313c…dad248e4
b827313ca271…603ddad248e46 archivos · ⁦6.4 KB⁩
EscaneoBajo1 hallazgo
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/coding/cpp-patterns@21cd568

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

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

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd568b827313cFirmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login