Refactor Python code after tests pass to improve readability and maintainability.
npx skills add https://github.com/meta-pytorch/OpenEnv --skill simplify
Please help me install this Agent Skill. Skill: simplify Source: https://github.com/meta-pytorch/OpenEnv/tree/main/.claude/skills/simplify Command: npx skills add https://github.com/meta-pytorch/OpenEnv --skill simplify
Refactor and clean up code after tests pass to improve readability, maintainability, and consistency, while preserving existing behavior.
Use the simplify skill to clean up a module after confirming tests pass, then run the test suite to verify everything remains green.
High-intent search queries and answers about installing and using this skill.
Refactor code after confirming your test suite passes green. Apply incremental changes—rename variables for clarity, extract helpers, remove duplication—then re-run tests to verify no regressions. This post-green-phase cleanup improves readability and maintainability while preserving behavior.
After tests pass, identify duplication and dead code by analyzing test outcomes and code smells. Extract repeated logic into helpers, simplify complex conditionals, and rename unclear variables. Re-test after each change to catch regressions early.
Refactor after tests pass to establish a green baseline and reduce risk of breaking changes. Starting with passing tests lets you apply targeted edits—variable renames, helper extraction, duplication removal—with confidence that re-testing will catch any regressions immediately.
Yes. The refactoring process applies to modules, utilities, and helpers across Python projects. Run tests first to establish a baseline, then clean up the code incrementally—removing dead code, improving names, extracting repeated logic—and re-run tests to confirm no behavior changes.
Look for duplication, dead code, unclear variable names, and overly complex conditionals. After tests pass, refactor these issues incrementally by renaming for clarity, extracting helpers to reduce duplication, and simplifying logic. Re-test after each change to ensure behavior stays intact.
CANTAGESTUDIOIdentify missing tests and establish a minimal safety net before refactoring.
VeraticusRefactor code incrementally with test-driven workflows and commit tracking.
a747895159Analyze source code to identify smells and propose refactoring opportunities.
daddiaApply single-issue code refactors after review while preserving behavior.
