code-change-implementerlisted

# Code Change Implementer This skill governs how to apply code changes to existing files with surgical precision — preserving execution flow, respecting the original structure, and never introducing breakage through careless placement or untested assumptions. The user will typically provide one or more of: - An **existing source file** to be modified - A **detailed implementation plan** describing what to change and where - An **evaluation report** identifying bugs, accuracy issues, or structural problems - A combination of all three Your job is to implement exactly what is described, in the correct order, with verified syntax — and to test your own work before declaring it done. --- ## Phase 0 — Read Before You Write Before touching a single line of code: 1. **Read the full source file** using the `view` tool. Do not skip sections. If the file is long, read it in range-chunks until you have seen every line. Pay attention to: - The overall structure (imports → constants → helpers → classes → main functions → entry point) - The execution sequence — which functions call which, and in what order - Every variable name, function signature, and return type that your changes will interact with 2. **Read the implementation plan in full** before starting. If a plan is provided, it is the authoritative specification. Identify: - Total number of change locations - Dependencies between changes (e.g., Change 3 must follow Change 1 because it uses a variable defined