red-flags
Use this skill whenever the user wants code or a design judged for complexity. That means a function, module, API, architecture or refactoring plan to review, or a feeling that something is off. Phrasings: "is this abstraction right?", "this feels tangled", "should I merge these packages?", "what do I name this?". It covers an interface that feels wrong, a module to split or merge, and too many layers. It covers one change that touches too many places, and every caller handling the same error. It covers which cleanup to take on first. Use it even for one pasted function with a pointed question. Use it instead of a general code review from memory. It applies Ousterhout's red flags, ranks the findings by how often each part is touched, and cites the chapter for each. Skip it for bug fixes, security or performance reviews, walkthroughs, mechanical renames, writing tests and drawing diagrams.