Skip to content
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-testingReverse engineering and fuzzing

c-testing

⁨C testing workflow for unit and integration tests: deterministic harnesses, CMake/CTest execution strategy, sanitizer-first debugging, and fuzzing escalation. Use when writing or fixing tests for C (C11+) modules, stabilizing flaky suites, or reproducing memory/UB bugs.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

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

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
nJxH1wBDQN…CXxDlSCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package6bd0ec7f…ea7eb3f4
6bd0ec7fb13c…0bd8ea7eb3f45 files · ⁦6.1 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/coding/c-testing@21cd568

Pragmatic workflow for reliable C tests and bug-finding.

When to activate

  • Adding unit tests for C functions
  • Building a small test harness around a module
  • Debugging failing tests or memory corruption
  • Enabling sanitizers or fuzzing to reproduce crashes

Core rules

  • Keep unit tests deterministic and isolated.
  • Avoid real network/time in unit tests.
  • Run ASan/UBSan in CI for memory and UB signal.
  • Reproduce failures in the smallest possible command first.
  • Do not hide memory/UB bugs behind test-only flags, retries, or inflated timeouts.
  • Pair with test-driven-development when implementing persistent code or bug fixes test-first.
  • Pair with testing-reliability for fixture/timing anti-patterns and systematic-debugging when the root cause is unclear.

Phase 1 — Reproduce with smallest scope

  • Run the single failing test first (ctest -R ... or direct binary invocation).
  • Capture exact command, seed/input, and environment variables.
  • Eliminate unrelated test noise before debugging.

Phase 2 — Strengthen harness determinism

  • Keep each test independent (no shared mutable global state).
  • Use explicit fixtures/setup-teardown for temp files and state reset.
  • Prefer table-driven tests for parsers and boundary-heavy functions.

Phase 3 — Sanitizer-first diagnosis

  • Run AddressSanitizer for memory corruption/UAF/OOB.
  • Run UndefinedBehaviorSanitizer for integer/shift/null/alignment UB.
  • Use stack-symbolized reports before stepping into debugger.

Phase 4 — CTest execution strategy

  • Label tests (unit, integration, slow, flaky) and run by label.
  • Use --output-on-failure and --rerun-failed in local loops.
  • Add per-test TIMEOUT to avoid hanging pipelines.

Phase 5 — Fuzzing escalation

  • Add libFuzzer target for parser/decoder/validator style APIs.
  • Seed corpus with valid and invalid minimal inputs.
  • Keep fuzz target stateless, deterministic, and side-effect free.

Fast triage checklist

  • Single failing test reproduced in isolation.
  • Failure reproduced under sanitizer build (if memory/UB suspected).
  • Backtrace/symbolization points to root cause function.
  • Regression test added for the fixed bug.
  • Full suite rerun (or label-targeted suite if justified) with no new failures.

Resources

Load on demand:

  • references/harness.md — harness structure, assertions, Unity/cmocka options
  • references/cmake-ctest.md — CMake/CTest patterns, labels, sanitizer presets, MinGW cross-compile
  • references/sanitizers-fuzzing.md — ASan/UBSan usage and a minimal fuzz target outline
  • references/debugging.md — gdb/lldb, Valgrind, MinGW objdump/nm, MSVC dumpbin/WinDbg, ASan env vars

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd5686bd0ec7fSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login