Continuing the series on how I design skills in Waza, this one is about how I built /check, the code review skill.
The starting point is simple. A model saying “it’s done” does not mean it is actually done. It can still leave behind broken logic, non-existent pieces, hidden
