Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/cpp-patternsAPIs, SaaS e identidade

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 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
G09mw12drz…TFaAsWDg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacoteb827313c…dad248e4
b827313ca271…603ddad248e46 arquivos · ⁦6.4 KB⁩
VarreduraBaixo1 achado
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/coding/cpp-patterns@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em 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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd568b827313cAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login