Video · Cole Medin ·
11 More Tiny Coding Agent Fixes With A Stupid Amount Of Payoff (Learn These Now)
In short
The video covers 11 recurring coding-agent problems and small fixes implemented through skills, rules, hooks, and planning workflows. It matters because these changes improve reliability, validation, control, focus, and token efficiency without requiring a complete overhaul of the agent setup.
Key points
- Use a separate reviewer agent or review skill when the agent claims unfinished work is complete.
- Require concrete testing evidence, including commands, outputs, and application screenshots.
- Validate applications like users with browser automation, not only unit and integration tests.
- Convert absolute rules and workflows into hooks that can enforce them reliably.
- Keep global rules lean and start a new conversation with a handoff document when context degrades.
- Customize planning so humans retain key decisions and small requests stay focused.
- Control sub-agent usage, testing depth, and tangents based on task scope and blast radius.
Written by an AI model from the video’s captions and description.
Coding agents keep hitting the same problems for you: saying the work is done when it isn't, tests that pass while the app is still broken, ignoring your rules, burning through your limits, etc.
In this story
A tool or model opens in the Heidelberg AI Curriculum: what it does, what it costs, how to start. A repo opens on GitHub.



