Sort common Codex signals into those that justify widening the change and those that call for a tighter boundary.
Sort each signal based on what it should do to scope in a disciplined Codex run. Legitimate reason to widen scope Signal to tighten or split scope The reproduced bug traces into a shared helper that owns the failing contract. One additional regression test is needed to prove the shared helper change end to end. The direct caller must change because the corrected helper output shape is different. A nearby file could use naming cleanup even though it is not part of the bug path. A reviewer cannot understand why one file is present and the justification is weak. Codex…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in