confirm-edit

To verify Git repository context before multi-file edits, run git commands against your target repository to check the origin URL, current branch, working tree status, and upstream divergence. An explicit confirmation template presents uncommitted and behind-upstream commit counts before proceeding.

Context switching causes accidental edits when working across multiple local paths and sites because the active branch or remote origin may not match the intended codebase. Validating the Git working tree state and upstream divergence prevents modifying the wrong repository.

You need repo validation safety checks for batch modifications when applying risky multi-file edits across 3 or more files, or when making any changes under specified path groups like ~/Repo/webs/ and ~/Repo/mykcs/, to ensure you are targeting the correct branch.

The best way to confirm the current branch before applying code changes is to execute git commands that fetch the remote origin URL and working tree status, then use an operator confirmation workflow requiring explicit approval before the edits run.

Yes, you can use an operator confirmation workflow for edits across multiple local paths. It applies to web and personal repo workflows, presenting a clear template so you can approve or provide an alternative target repository before proceeding with modifications.

During repo validation, if your working tree has uncommitted changes, the safety checks will detect them and present the uncommitted commit counts in the confirmation template, requiring you to explicitly approve before proceeding with the multi-file edits.