explain-change

To document code change rationale, link the actual diff to the problem, proposal, requirements, architecture decisions, and tests. This creates a durable artifact for PR handoffs, ensuring future maintainers understand the complete decision trail and verification evidence.

Code change traceability provides end-to-end linkage from the diff back to the problem, proposal, and verification findings. For post-implementation audits, it captures the decision trail and review resolutions, proving exactly why specific code modifications were made.

Create a decision trail by recording an explicit scope and risk discussion alongside the diff rationale. When material findings exist, include a comprehensive review-resolution summary that documents the alternatives considered, ensuring full architectural context.

Yes, you can link code diffs to plan milestones and requirements. This workflow integration maps the actual code modifications directly to the proposal and architecture decisions, verifying that the AI-assisted changes meet the original project specifications.

The best way to resolve material findings is to generate a review-resolution summary within the change artifact. This summary captures the alternatives considered, risk considerations, and the final verification evidence, closing the loop on the audit.