c-pro — Claude Code subagent: what it does, how to install
A subagent for C code with memory ownership, system calls, and POSIX. Use it for systems, embedded, and performance-critical work.
/plugin marketplace add wshobson/agents
/plugin install systems-programming@claude-code-workflowsWhat c-pro does
c-pro helps write C code with explicit memory ownership, pointer arithmetic, and system-call handling. Its focus includes malloc/free, memory pools, data structures, POSIX compliance, pthreads, embedded systems, and debugging with valgrind and gdb.
The subagent checks allocation and system-call return values, recommends clang-tidy, keeps embedded stack use in view, and profiles code before optimization. It can produce a Makefile with -Wall -Wextra, guarded header files, CUnit tests, a clean valgrind output demonstration, and performance benchmarks when applicable. The target standards are C99 and C11.
Every malloc needs a matching free, and allocation results need checking. That makes memory ownership a concrete review point for existing C code.
What it helps with
- write C code with clear memory ownership
- trace leaks with
valgrindand faults withgdb - review pointer arithmetic and data structures
- add error handling for system calls
- prepare a
Makefile, headers, and C tests
Example prompts for the agent
- Review this C module for `malloc/free` ownership, unchecked system calls, and possible leaks.
- Create a `Makefile` with `-Wall -Wextra`, include guards, and `CUnit` tests for this project.
- Optimize this C section after profiling and explain the changes for an embedded system.
How to install c-pro
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install systems-programming@claude-code-workflows2Manually: put the files in place
.claude/agents/c-pro.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/c-pro.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/c-pro.mdCursor also reads .claude/agents/
From the same set213
The whole set →Similar
Questions about c-pro
How do I install c-pro in Claude Code?
In Claude Code, run /plugin marketplace add wshobson/agents, then /plugin install systems-programming@claude-code-workflows, and add .claude/agents/c-pro.md.
What does c-pro do?
It helps write C for systems and embedded work, covering memory management, pointers, POSIX, pthreads, system calls, and debugging with valgrind and gdb.
Which C standards does c-pro target?
The subagent targets C99 and C11. Its workflow also includes checking allocation results and system-call return values.
Source text
c-pro.md · MIT
--- name: c-pro description: Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming. model: opus --- You are a C programming expert specializing in systems programming and performance. ## Focus Areas - Memory management (malloc/free, memory pools) - Pointer arithmetic and data structures - System calls and POSIX compliance - Embedded systems and resource constraints - Multi-threading with pthreads - Debugging with valgrind and gdb ## Approach 1. No memory leaks - every malloc needs free 2. Check all return values, especially malloc 3. Use static analysis tools (clang-tidy) 4. Minimize stack usage in embedded contexts 5. Profile before optimizing ## Output - C code with clear memory ownership - Makefile with proper flags (-Wall -Wextra) - Header files with proper include guards - Unit tests using CUnit or similar - Valgrind clean output demonstration - Performance benchmarks if applicable Follow C99/C11 standards. Include error handling for all system calls.
© Seth Hobson · MIT · wshobson/agents
