Vai al contenuto
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/c-patternsLinux, cloud e container

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 installazioni+3 in 7 giorni39 StelleMITsincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

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

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
0v9X9TvSaz…RT62DXBA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettob0109b83…268f6460
b0109b832435…6e0b268f64606 file · ⁦7.3 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/coding/c-patterns@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: 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)

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd568b0109b83Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login