← ClaudeAtlas

behaviour-equivalencelisted

Prove that a rewritten, migrated or refactored component behaves the same as the old one with a golden-master comparison — record inputs and outputs at a boundary (HTTP, function calls, batch files, DB writes, events) from production-shaped traffic and edge cases, run the old system twice to find its nondeterminism, normalise narrowly field by field, replay against the new one, triage every difference as defect, intended change (with a named approver) or missing normalisation, and give a verdict of EQUIVALENT, EQUIVALENT EXCEPT LISTED CHANGES, NOT EQUIVALENT or NOT PROVEN. Use when the user asks "does the new one behave the same as the old one", "can we sign off the rewrite", "are these diffs just noise", wants a golden-master, approval or shadow-traffic comparison, a parity check between old and new outputs, or says "prove behaviour equivalence".
sananthanarayan/skilldrop · ★ 2 · AI & Automation · score 65
Install: claude install-skill sananthanarayan/skilldrop
# behaviour-equivalence Proves, or fails to prove, that a new implementation does what the old one did, at a boundary both share. The old system is the specification, bugs included. The output is a verdict, the differences behind it, each one classified, and the input classes the verdict covers. Planning the refactor steps is `refactor-plan` (which names a golden-master test as step one); this skill runs that comparison and judges it. Migration phases, backfill and cutover gates are `migration-plan`; this skill supplies the parity evidence a gate asks for. A test plan for new behaviour is `test-plan-generator`. Finding where the old code lives is `codebase-tour`. ## How to respond **Four rules come before the steps and outrank them:** - **Answer what was asked, first.** The first line is the verdict word and the reason: ✅ *"NOT EQUIVALENT: the new service computes delivery dates in UTC, so orders placed after 23:00 London time get a date one day early."* — ❌ a table of match counts, or "mostly the same". - **Use only what you were given.** No invented cases, traffic volumes, approvers, dates or root causes. A cause is stated only when the code or the data shows it; otherwise it is a check to run. - **Deliver from what you have.** With recordings, compare them and give the verdict. With only a description, design the comparison and say no verdict exists yet. Ask only when there is no component to compare at all. - **Write for someone who has never heard of this skill.** N