Delete legacy compatibility code only after verifying live call sites and public contracts.
npx skills add https://github.com/joshka0/foxctl --skill foxctl-no-slop
Please help me install this Agent Skill. Skill: foxctl-no-slop Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-no-slop Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-no-slop
Prevents sloppy refactors by forcing evidence-backed decisions before deleting legacy UX, routes, wrappers, fallbacks, or duplicated rules, so you don’t accidentally break hidden callers or contracts.
Use the foxctl-no-slop skill to produce an evidence table and an end-state deletion plan for a change that includes compatibility suspects like legacy routes or wrappers.
High-intent search queries and answers about installing and using this skill.
To safely delete legacy routes and compatibility wrappers, you must first gather caller-proof evidence using exact context grep, repo graph searches, and semantic code search to verify the surfaces are not live call sites or required public contracts.
Caller-proof evidence in compatibility cleanup is validation data proving a legacy surface has no live callers, generated by combining exact context grep, repo graph reference expansion, and semantic code search to account for naming drift.
Removing fallback branches and duplicated rules without breaking hidden callers requires searching exact text hits, checking repo graph inbound and outbound references, and validating semantic reach before executing the deletion plan.
Semantic code search is used to find legacy surfaces when names drift across a codebase, complementing exact context grep and repo graph expansions to ensure all inbound references are proven dead before deleting compatibility cruft.
The best way to consolidate duplicated rules and historical complexity is to refactor around one clear product surface, using an evidence table to dictate a structured end-state deletion plan with deleted, kept, and residual-risk sections.
You should not delete migration helpers and mode flags when caller-proof searches reveal they are still active live call sites or required public contracts, leaving them documented in the residual-risk section of the end-state plan.
joshka0Replace legacy outward contracts with a single canonical contract by removing compatibility logic.
susomejiasRefactor codebases to align with end-state architecture and remove dead code.
parcadeiAnalyze code structure using AST, call graphs, CFG, DFG, and PDG.
TrebuchetDynamicsAnalyze repository docs and caller paths to identify testable seams.
