Produce behavior-preserving refactor commit sequences with green test gates.
npx skills add https://github.com/kapilvirenahuja/garura --skill garura-refactor
Please help me install this Agent Skill. Skill: garura:refactor Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/refactor Command: npx skills add https://github.com/kapilvirenahuja/garura --skill garura-refactor
Prevents behaviour changes while restructuring code by enforcing a green test baseline, isolation of refactor moves into atomic commits, and a final evidence report that proves what stayed the same.
Run garura:refactor for a specific target scope and restructuring goal, providing constraints, an out-of-scope list, and a time-box, so it pins the baseline with tests and generates an approval-ready refactor plan.
High-intent search queries and answers about installing and using this skill.
You preserve observable behaviour by enforcing a green test baseline, mapping the blast radius, and isolating changes into atomic commits gated by passing tests. This sequence proves the public API and functional output remain unchanged throughout the refactor.
Characterization tests are safety nets that lock in current code behaviour before restructuring. You need them when existing test coverage is thin, ensuring your refactor commits do not accidentally alter the current observable outputs.
You structure atomic refactor commits by isolating each structural change into a single commit that keeps the test suite green. Pin a clean working tree baseline first, then gate every commit with passing tests to prove behaviour preservation.
You map blast radius by analyzing the scope impact of your target restructuring goal before execution. This identifies affected dependencies and public API changes, requiring a human-approval checkpoint before any refactor commits are generated.
Yes, this refactoring approach supports deterministic, enterprise-grade delivery. It enforces a clean working tree, a green baseline with characterization tests, and a final report with an API diff to prove behaviour preservation for enterprise systems.
Out-of-scope work must be deferred to prevent behaviour drift during refactoring. By moving non-restructuring tasks to a FOLLOWUPS.md file, you ensure atomic commits remain focused on structural changes that maintain a green test suite and an unchanged public API.
rshankrasGenerate characterization tests for uncovered code before refactoring.
LayerDynamicsAudit git diff changes against the active project plan.
kivo360Orchestrate SPEC-first TDD workflows with SPEC, TEST, CODE, and DOC phases.
JiggerFMap PR diff files to affected test suites and run targeted vitest commands.
