refactor-change-report

Refactor change reports provide structured documentation summarizing what changed, why, and what to verify. Generate a template-driven report with sections covering goals, metrics, changes made, key decisions, and risks to enable thorough review and knowledge sharing after refactoring work.

A complete refactoring summary includes before/after metrics, specific changes made, the goals behind those changes, key architectural decisions, what was intentionally not changed, and identified risks or follow-up tasks. This structured approach accelerates review cycles and documents rationale for future reference.

Generate a change report immediately after completing a refactoring session to capture decisions while fresh and create a review-ready document. This timing preserves context, accelerates code review, and establishes a knowledge artifact for onboarding and future maintenance.

Yes. Change reports document refactoring rationale and metrics, enabling teams to identify patterns, validate improvements, share knowledge across the organization, and build institutional understanding of code-quality decisions and their outcomes.

A change report is a focused, post-refactor summary covering goals, metrics, changes, decisions, and risks in a standardized template. It differs from general documentation by tying specific code changes to measurable outcomes and enabling structured review rather than narrative explanation.