I built an open-source skill that stops coding agents from overthinking simple tasks

Reddit r/AI_Agents Tools

Summary

An open-source agent skill classifies coding tasks into S/M/L/XL complexity classes to set appropriate execution depth, preventing overthinking simple fixes and enabling evidence-based reclassification.

Hi, I built Code Complexity Router, an open-source agent skill that classifies coding tasks as S, M, L, or XL before execution. The goal is simple: a two-line fix should not receive architecture-level exploration, while a risky migration should not receive typo-level verification. These complexity classes define the agent’s starting execution depth—not hard limits on what it is allowed to investigate. Based on the available evidence, the skill adjusts: context gathering planning depth verification depth recommended model tier token and tool-use discipline Example: Small task — rename a button The agent starts with a focused inspection: inspect the target file and one related file when useful; make the smallest safe change; run focused validation; avoid broad searches unless evidence suggests wider impact. If the first inspection reveals additional call sites, shared values, generated files, indirect dependencies, or sensitive behavior, the task is immediately reclassified—before any code is changed. The skill distinguishes between: inspection-based escalation, when repository evidence disproves the initial scope; failure-based escalation, when the first implementation hypothesis or validation fails. It also maintains a compact Task Scope Contract containing the accepted scope, supporting evidence, known exclusions, focused validation, and escalation conditions. This helps preserve continuity across model changes and resumed sessions. When automatic model switching is unavailable, the skill controls workflow depth instead of claiming to change the selected model. GitHub repository link in the comments. I’m looking for feedback on: incorrect S/M/L/XL classifications; missing escalation triggers; Codex compatibility; Task Scope Contract usefulness; whether the skill reduces unnecessary context, tool calls, and verification effort without hiding complexity. I’m also preparing A/B benchmarks comparing tasks completed with and without the skill.
Original Article

Similar Articles

@liumengxinfly: Tried the improve-codebase-architecture skill. The author says running it periodically can clean up AI slop. I ran it and it cleaned up all the code I wrote by hand before using AI.

X AI KOLs Timeline

This article shares a developer's experience using the improve-codebase-architecture skill from mattpocock/skills, which claims to clean up AI-generated slop but apparently also removes code written before using AI. The skill set is a collection of small, composable agent skills for real engineering.