Plan structural refactors as commit-grain tasks with green tests.
npx skills add https://github.com/iusztinpaul/squid --skill refactor-iusztinpaul
Please help me install this Agent Skill. Skill: refactor Source: https://github.com/iusztinpaul/squid/tree/main/skills/refactor Command: npx skills add https://github.com/iusztinpaul/squid --skill refactor-iusztinpaul
Plan a refactor as an ordered, commit-grain Tasks Plan with structural acceptance criteria (test suite green at every step, no behaviour diff, named module/coupling invariants). Output is a feature-shaped plan that /night can execute end-to-end. Trigger when the user says "/refactor", asks "plan a refactor of X", "extract Y from Z", "split this module", "rename across the codebase", or describes a structural change with no user-visible feature behind it.
Say /refactor with your goal to generate a deterministic, commit-grain Tasks Plan that keeps main green.
High-intent search queries and answers about installing and using this skill.
To plan a code refactor without breaking tests, you generate an ordered, commit-grain Tasks Plan where each step includes structural acceptance criteria that keep the test suite green. This ensures tasks are reversible and behavior remains unchanged throughout the process.
The best way to extract a module safely is to sequence the structural changes into commit-grain tasks with explicit acceptance criteria. This approach documents coupling invariants and verifies the public API remains unchanged after every task.
Yes, you can use this planning approach for renaming modules across the codebase. It applies to non-behavioral structural changes like renames and layer cleanups, ensuring the main branch stays green and the overall behavior remains unchanged.
You create a step by step plan for software modularization by triggering the planner with your structural goal, which outputs a deterministic, feature-shaped Tasks Plan. Each commit-grain task includes a definition of done and acceptance criteria to guarantee safe execution.
You should avoid using a commit-grain task plan for refactoring when the change involves user-visible features or behavioral differences. This planning approach is specifically designed for non-behavioral structural changes where the public API remains unchanged.
alffeiEnforce Red-Green-Refactor by requiring failing tests before coding.
ynotradioVerify agent-created pull requests with local tests and Playwright screenshots.
llama-farmStage changes, create conventional commits, push to origin, and open a PR via gh CLI.
1ambdaRefactor code with behavior-preserving changes validated by automated tests.
