agentleFS
Sign inStart free
CassetteTapeCrackleCassetteTapeCrackle/claude-starters/skills/clean-code-c/SKILL.md

clean-code-c

Skill1 starsChanged 3 months agoMITView on GitHub

Use when writing or reviewing C — deeper idioms (ownership discipline, bounded string ops, allocation checking, linkage, initialization) beyond clang-tidy.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document ownership at every allocating function: who frees, when.

    line 11
  2. Very specific:

    Check every malloc/realloc/calloc return.

    line 12
  3. Very specific:

    No VLAs; no unbounded strcpy/strcat/sprintf — use snprintf and bounded copies with explicit sizes.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Clean-code C (depth)

On top of the base rules (C11, CMake, clang-tidy, ASan+UBSan, Unity/CMocka).

Memory & ownership

  • Document ownership at every allocating function: who frees, when. One owner; transfer explicitly.
  • Check every malloc/realloc/calloc return. Free on every path (goto-cleanup pattern for multi-resource functions).
  • Set freed pointers to NULL if reused. Never return pointers to stack locals.

Safety

  • No VLAs; no unbounded strcpy/strcat/sprintf — use snprintf and bounded copies with explicit sizes.
  • sizeof(*ptr) (variable) over sizeof(Type) so it survives type changes. Initialize every variable at declaration.

Structure

  • static for internal-linkage functions/globals; expose the minimum in headers.
  • const-correct parameters; size_t for sizes/indices. Small functions; early returns; one responsibility per file.

Smells

  • An allocation whose free path isn't obvious → add the ownership comment or restructure with goto-cleanup.
  • sprintf/strcpy into a fixed buffer → bounded call.
  • Uninitialized variable read (UBSan will catch it) → initialize at declaration.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free