What problem does it solve? Refactoring a repository's scripts/ directory is risky: dead scripts are hard to distinguish from load-bearing ones, shell-to-Python ports silently change output and exit codes, and golden artifacts consumed by other test suites break when logic moves. This Skill provides an evidence-driven workflow that converts scripts to the repo's tooling language, moves logic into src/ with TDD tests, and proves behavior parity with diffs instead of eyeballing. ## Core Features & Use Cases - Usage-evidence inventory: Classify every script as LIVE or HISTORICAL using git ls-files and ripgrep-backed reference tracing, so removal candidates carry a written evidence trail. - Thin-wrapper layout with TDD: Preserve existing call sites via thin entrypoints that import logic from scripts/src/, with pytest tests written first and expected values derived by executing the legacy code. - Byte-identical port verification: Run old-vs-new CLI parity harnesses that diff stdout, stderr, exit codes, and output artifacts, using PATH shims for external tools like dotnet. - Use Case: Converting a verify-tool-package.sh script to Python while a CI gate requires identical messages and exit codes — the Skill's checklist preserves stream splitting, print ordering, and exit-code propagation, and the parity harness proves the contract. ## Quick Start Refactor this repository's scripts directory by converting shell scripts to Python, moving logic into src with tests written first, and pruning unused scripts based on usage evidence.
