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/c-patternsLinux, cloud e containers

c-patterns

⁨C language patterns and best practices for safe, maintainable C: ownership, API contracts, error handling, integer safety, portability, and concurrency boundaries. Use when writing or reviewing C code (C11+), designing module interfaces, refactoring legacy C, or hardening low-level code paths.⁩

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/c-patterns

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

AssinaturaAssinado, ed25519
0v9X9TvSaz…RT62DXBA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacoteb0109b83…268f6460
b0109b832435…6e0b268f64606 arquivos · ⁦7.3 KB⁩
VarreduraBaixo1 achado
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/coding/c-patterns@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em English.

This skill focuses on safe C: explicit ownership, explicit errors, predictable control flow, and contracts that survive refactors.

If you’re writing tests, use c-testing.

When to activate

  • Writing/refactoring C modules and APIs
  • Reviewing for memory safety and integer safety
  • Designing error-handling conventions and cleanup paths
  • Hardening code for sanitizer/static analysis adoption
  • Porting C code across GCC/Clang/MSVC/MinGW

Core rules (high signal)

  • Make ownership explicit: allocate/free at the same abstraction level.
  • Use a consistent error strategy (return codes, out-params) and document it in headers.
  • Avoid in-band error indicators when possible.
  • Use a single-exit cleanup path for functions managing multiple resources.
  • Treat integer conversions and size calculations as potential bugs.

Phase 1 — Define API contract first

Before coding:

  • Define ownership of every pointer parameter (borrowed, owned, transferred).
  • Define preconditions/postconditions in the header, not only in comments inside .c.
  • Define error domain (enum or code space) and whether errno is used.

Phase 2 — Implement with explicit lifetimes

  • Use create/destroy, init/deinit, or open/close pairs consistently.
  • Keep one cleanup exit path for multi-resource functions.
  • Do not mix allocator families (malloc/free vs custom pool vs Win32 heaps).

Phase 3 — Harden integer and bounds logic

  • Use size_t for sizes/counts and guard all multiplication/addition used in allocation.
  • Validate all signed/unsigned conversions and indexing arithmetic.
  • Reject impossible sizes early (n == 0, n > MAX_ALLOWED, overflow guards).

Phase 4 — Concurrency boundaries

  • Prefer immutable data or message passing where possible.
  • If locks are needed, document lock ownership and lock order in header comments.
  • Use atomics for single-value state; mutexes for compound invariants.

Phase 5 — Toolchain-aware portability

  • Keep warning set strict on all compilers (GCC/Clang/MSVC).
  • Avoid UB-dependent behavior and compiler-specific assumptions.
  • Guard compiler-specific attributes/macros with feature checks.

Quick review checklist

  • Every pointer has clear ownership semantics in the API.
  • Every non-trivial function has deterministic cleanup path.
  • Every allocation arithmetic path has overflow guard.
  • Every error path returns actionable status.
  • Concurrency primitives protect explicitly documented data.
  • Code builds clean with strict warnings on at least two toolchains.

Resources

Load on demand:

  • references/error-handling.md — error policy, return codes, cleanup patterns
  • references/memory-ownership.md — allocation/free rules, zero-length alloc, free-null
  • references/integers.md — overflow, size_t usage, bounds checking
  • references/concurrency.md — pthreads, C11 atomics, Win32 threads, race detection
  • references/tooling.md — warnings, sanitizers, static analysis, binary inspection (MinGW/objdump, MSVC/dumpbin, Linux tools)

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 202621cd568b0109b83Assinada–

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