{"id":77020,"plugin_id":"plugins_6ab41ed5b8c4819199eb5bbf91ce25f5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:19.214Z","digest":"89f7a6123410bfd413decdbff6030b411145b3a23e192e8df8b8b6b9fad99381","against":null,"payload":{"description":"Improve maintainability or structure of existing code without unintended changes to externally observable behavior.","included_files":[],"name":"refactor-safely","skill_md_contents":"---\nname: refactor-safely\ndescription: Improve maintainability or structure of existing code without unintended changes to externally observable behavior.\n---\n\n# Refactor Safely\n\nUse this skill only for its stated purpose. Follow the shared source-of-truth, permission and evidence rules in `../../references/workflow-contract.md`. Read `../../references/behavior-preserving-refactors.md` for detailed method when necessary.\n\n## Procedure\n1. Define behavioral invariants, public interfaces, state/order semantics and relevant performance contracts.\n2. Establish characterization or existing regression tests before broad edits.\n3. Refactor in small steps, reuse established patterns and minimize diff churn.\n4. Compare outputs/contracts before and after; run targeted tests when possible.\n5. Report deliberate behavior changes separately, or state none intended.\nDo not add new frameworks or migrate storage unless explicitly in scope.\n\n## Handoff rule\nState actual artifacts or grounded code findings and validation status. Never invent file paths, executed tests, tool access, or completed subagent work. Keep output proportionate to the user request.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}