Scenario Readiness Review

To check git readiness before committing scenario changes, you can run a unified review polling process that queries git state and diff status to ensure work coherence. This health briefing evaluates code quality and detects suspicious edits before a commit decision.

A scenario readiness review is a pre-commit health check that combines git-control-tower readiness signals with git diff and status validation. It assesses whether uncommitted scenario work is coherent, complete, and safe to commit without modifying repository state.

To validate uncommitted git changes for code review, inspect repo status, repo diff, and repo history to analyze file count, scope, and coherence. This validation detects sprawling edits and ensures the changes meet readiness criteria before committing.

No, the scenario readiness review does not modify repository state during assessment. It adheres to strict guardrail instructions that prevent state modification, ensuring the evaluation only reads git diff, status, and review endpoint data to determine commit readiness.

You should run a code quality assessment before a git commit whenever a scenario has uncommitted work needing a health briefing. This prevents prematurely committing changes by verifying that server-provided readiness signals and git change validation are green.

When blocking issues surface during a git readiness check, the decision protocol delegates remediation with precise findings. If readiness is green, it instead triggers the prompt-manager director-swarm decision with detailed rationale to proceed with the commit.