Git Hygiene & Clean Tree Manager

Git hygiene requires enforcing a clean tree mandate that automatically rejects commits containing secrets, temporary files, or build artifacts before they enter source control. Pre-push validation protocols scan staged changes to maintain repository integrity.

A clean Git tree mandate is a strict protocol that prevents unwanted files like scratch scripts and build outputs from polluting source control. You need it to maintain a manageable codebase and secure sensitive data across multiple agents.

Managing scratch scripts requires guiding their lifecycle within the Git repository to ensure temporary files are deleted after use. This hygiene protocol prevents obsolete scripts from accumulating in the project history.

Pre-push validation operates across multiple agents to ensure repository hygiene before every commit. You can run `git status` before pushing to identify and reject unintended files staged for source control integration.

The Git hygiene protocol operates across multiple agents to maintain source control integrity. It enforces a clean tree mandate to automatically identify and reject commits containing secrets or build outputs throughout the development lifecycle.

Automated Git hygiene focuses strictly on preventing the commitment of temporary files, secrets, and build artifacts. It does not alter existing repository history, but rather validates pre-push states to stop unwanted files from entering source control.