Embedded C Discipline with Balemarthy Vamsi

Not a checklist. A system that runs itself.

You already know the rules — volatile on shared state, nothing blocking inside an ISR, bounds on every buffer. You've been the one enforcing them, from memory, in every review, for years.

Embedded C Discipline is the rulebook plus the scripts that mean you don't have to be the only enforcement mechanism anymore. It's a Claude Skill — install once, works everywhere you use Claude — built around six deterministic Python checkers, not vibes-based AI review.

What's inside:

• The rulebook: type safety, volatile/const correctness, ISR safety, memory bounds, naming conventions, formatting — the discipline you already carry in your head, written down
• Six Python checkers, zero dependencies: ISR safety, memory/bounds safety, hardware register access, naming, formatting, module structure
• One command that runs all six and reports findings line-by-line, compiler-style
• Test fixtures — one deliberately broken, one clean — so you have evidence of what it catches before you trust it on your own code
• Works standalone too: drop it into a pre-commit hook or CI pipeline, no Claude required

Built for: embedded engineers tired of saying the same eleven things in every code review, who want leverage instead of another checklist.