Refactor a single module with tests after every edit.
npx skills add https://github.com/linenoize/topia --skill surgeon-linenoize
Please help me install this Agent Skill. Skill: surgeon Source: https://github.com/linenoize/topia/tree/main/skills/surgeon Command: npx skills add https://github.com/linenoize/topia --skill surgeon-linenoize
Surgeon enables disciplined, low-risk refactoring when a codebase needs improvement but cannot afford broad or speculative changes. It keeps the work constrained to one module per session, so changes stay understandable, testable, and reversible.
Use surgeon to safely refactor the target module in a single, test-validated session without exceeding the five-file blast radius.
High-intent search queries and answers about installing and using this skill.
Legacy code refactoring is safest when constrained to one module per session. This workflow enforces a strict five-file blast radius, verifies safeguards, and runs tests after every edit to incrementally rewrite tightly coupled modules without breaking existing behavior.
Incremental module rewriting uses pattern-guided changes like Strangler Fig or Branch by Abstraction. This approach isolates legacy behavior and applies per-edit testing, ensuring each refactor step remains understandable, testable, and reversible without broad speculative changes.
Yes, test coverage is a prerequisite for safe refactoring. This safety-first workflow requires preexisting safeguard coverage to validate behavior, stopping immediately if tests fail after an edit to prevent regressions in the target module.
A blast-radius check limits architectural refactoring impact by refusing changes that exceed a five-file scope. This constraint keeps the work focused on a single module, making changes understandable and reversible while preventing unintended damage to the broader codebase.
Yes, pattern-guided refactoring supports Strangler Fig, Branch by Abstraction, Expand-Migrate-Contract, and Extract & Simplify. These patterns guide the refactor shape depending on the module's architecture, ensuring disciplined and low-risk structural changes.
After safe code refactoring, the session ends with a production-ready follow-through. This process includes a final code review, a commit of the isolated changes, and a journal update to leave a clear audit trail of the incremental structural improvements.
accelerate-dataConstruct behavior-driven unit tests to validate core functionalities and prevent regressions.
thimsluggaIdentify and apply small, verifiable improvements to software processes and code quality.
I-OnlabsAudit codebases across architecture, quality, security, and performance to produce prioritized health reports.
ZeiZelPlan and apply automated code, configuration, and dependency migrations.
