‹ Back to apps
Code Radius
Don’t edit until you know what the change will touch. Code Radius makes AI coding agents map the impact radius of a feature, bugfix, rename, or migration before writing code—cited entry points, callers, tests, infra, and risks—then implement only inside a bounded edit set. No API keys. Portable Agent Skills for Cursor and other Agent Plugins clients.
What’s inside
3 skills- Skillradius-gateCode Radius gate — enforce impact-radius recon before code edits. Use when about to modify files without an Impact Radius Report, when scope is expanding past the agreed edit set, or when the user says don't edit yet, run radius first, code radius first, gate this change, preflight first, or stop and map impact. Blocks implementation until Code Radius completes or the user explicitly overrides (skip radius / just do it).
- Skillradius-verifyCode Radius verify — check that a completed or in-progress diff stayed inside the agreed impact-radius edit set. Use after implementing a change mapped with Code Radius, before opening a PR, or when the user asks to verify edit set, check scope drift, confirm we only touched the radius, or audit out-of-scope files. Reports in-scope changes, out-of-set files, missing tests from the report, and a verdict (clean / extend-radius / revert-out-of-set).
- SkillradiusCode Radius — map the impact radius of a proposed code change before editing. Use for features, bugfixes, refactors, renames, migrations, API/schema changes, auth, payments, permissions, shared utilities, or when the user says code radius, map the radius, impact radius, change scope, affected surface, what will this touch, what breaks, don't edit yet, bound the edit set, preflight this change, or scope this PR. Also use when about to modify code with unclear callers or cross-module risk. Produces a cited Impact Radius Report (entries, callers, shared core, contracts, tests, infra, risks) and a bounded edit set. Do not implement until the report is delivered unless the user explicitly skips Code Radius.