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 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/c-patternsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packageb0109b83…268f6460
b0109b832435…6e0b268f64606 files · 7.3 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/coding/c-patterns@21cd568
On this page
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.
Recommended workflow
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 (
enumor code space) and whethererrnois used.
Phase 2 — Implement with explicit lifetimes
- Use
create/destroy,init/deinit, oropen/closepairs consistently. - Keep one cleanup exit path for multi-resource functions.
- Do not mix allocator families (
malloc/freevs custom pool vs Win32 heaps).
Phase 3 — Harden integer and bounds logic
- Use
size_tfor 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 patternsreferences/memory-ownership.md— allocation/free rules, zero-length alloc, free-nullreferences/integers.md— overflow, size_t usage, bounds checkingreferences/concurrency.md— pthreads, C11 atomics, Win32 threads, race detectionreferences/tooling.md— warnings, sanitizers, static analysis, binary inspection (MinGW/objdump, MSVC/dumpbin, Linux tools)
Files in this version
references/513.2 KB
- concurrency.md3.4 KB
- error-handling.md2.1 KB
- integers.md1.9 KB
- memory-ownership.md2.0 KB
- tooling.md3.9 KB
- SKILL.md3.7 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | b0109b83 | Signed | – |
More from AeonDave
All from this publisherMore in Linux, cloud and containers
See the category- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login