reasoning-guard

Use when coding agent exhibits reasoning path failures during multi-turn coding sessions: error accumulation across iterations, repeated edits on the same location without convergence, excessive token consumption without measurable progress, or semantic regression where code quality degrades across edits. Detection is session-context-based (no hooks required); the agent applies correction prompts proactively within the current conversation. Also use when asked to "apply reasoning guard", "check my reasoning path", "stop and rethink", or "am I going in circles". Do NOT use when the agent is producing correct output steadily.