Review / Verify Change

Munk AI is opinionated about validating real product changes, not only replaying scripts.

Review-first verification

The review and verify change workflows are meant to start from a code change summary and changed files. From there, the system can generate findings, risks, and practical verification hints.

Why it matters

This is useful when:

• a developer wants stronger confidence before merge
• a coding agent has finished implementation and needs grounded verification
• the team wants structured follow-up checks instead of generic review comments

Typical input shape

You usually provide:

• an app identifier
• a change summary
• one or more changed files
• a config file

The output is not just a pass or fail. It is meant to guide verification work with more structure.