Enforce Karpathy active coding rules
karpathy-coderpluginsetup L2★17,464
alirezarezvani/claude-skills ↗What it does
Enforce active coding discipline using Karpathy's four principles
Best for
Catching unsafe abstractions and unfocused changes before code review by surfacing assumptions, complexity drift, and vague goals
Inputs
- · code change
- · assumptions list
- · verifiable goals
Outputs
- · complexity report
- · surgical diff review
- · assumption linter output
- · goal verifier report
Requires
- · 4 stdlib Python tools (complexity_checker, diff_surgeon, assumption_linter, goal_verifier)
- · pre-commit hook
Preconditions
Project has git repo initialized; pre-commit hook installed; developer supplies assumptions and goals
Failure modes
Complexity checker flags refactoring that actually simplifies upstream usage; assumption linter produces false positives on implicit type conversions; pre-commit hook slows commit by 5+ seconds
Trust signals
- · Based on Karpathy's 4 principles (surface assumptions, keep simple, surgical changes, verifiable goals)
- · 4 stdlib-only Python tools
- · Pre-commit hook integration
- · Review agent + /karpathy-check command included