Backprop
juliusbrussee/cavekitWhen a bug is found in your code, you can now prevent it from ever coming back. This process adds a rule to your specification that catches the same mistake. It is like teaching your system a new lesson so it never forgets.
The method is called backprop. It works in six simple steps. You trace the bug, analyze the cause, propose a new invariant, generate a test, verify the fix, and log everything. The result is a stronger specification and a safer codebase.
This approach works for test failures, user reports, post-mortems, or direct requests. It turns every bug into a permanent improvement.
Add Backprop skill to your workflow
Global
mkdir -p ~/.claude/skills/backpropProject
mkdir -p .claude/skills/backpropSource Repository
More Code Review & Quality Claude Code Skills
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective