km:intent-review

To verify uncommitted changes match original intent, reconstruct explicit requests and agreed design decisions from conversation history, compare git diffs and change statistics, and produce a structured report with HIGH/MEDIUM/LOW findings and remediation guidance.

An intent review for code changes is a verification process that ensures uncommitted file changes satisfy the user's original request and agreed design decisions by reconstructing requirements from conversation history and comparing them to actual git diffs.

You need to validate code changes against conversation history when an active context or review record exists and you want to prevent scope creep or unintended regressions before committing work produced during pair-programming sessions.

Yes, you can check if your git diff satisfies agreed design decisions by mapping implemented changes to reconstructed requirements and flagging gaps by severity, producing a structured report with remediation guidance.

The best way to prevent scope creep before a git commit is to reconstruct explicit requests and reasonable implicit expectations from conversation transcripts, then compare file change statistics to flag any scope violations by severity.

No, intent review requires a conversation context or review history to exist, because it must reconstruct explicit requests and agreements from conversation transcripts to validate changes made before committing.