Quiz the user on a git branch's changes to verify genuine comprehension. Rather than passively reading diffs, the user answers targeted questions covering: runtime behavior, embedded assumptions, failure points, edge cases, API design decisions, data model changes, data flows, security implications, performance impacts, and dependencies & integration effects. Score their understanding and surface any gaps.
Run git diff main...HEAD to collect all changes on the current branch. If the branch has no diff against main, inform the user and stop.
Read through every changed file. Build a mental model of:
Úselo cuando el usuario quiera verificar su comprensión de los cambios de código de una rama al ser interrogado sobre el comportamiento del tiempo de ejecución, suposiciones, puntos de falla y casos extremos en lugar de simplemente leer diferencias. Fuente: buildrtech/dotagents.