Git Hygiene & Clean Tree Manager

Name: Git Hygiene & Clean Tree Manager
Availability: InStock
Author: CryptoDisco

Enforce clean Git trees by blocking temporary files, secrets, and build artifacts.

Updated Jan 31, 2026

Search Tags:#git #devops #security #clean code #repository management #hygiene

Ready to run

npx skills add https://github.com/cryptodiscolab/Crypto_Discovery_App --skill git-hygiene-clean-tree-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Git Hygiene & Clean Tree Manager
Source: https://github.com/cryptodiscolab/Crypto_Discovery_App/tree/main/.agents/skills/git-hygiene
Command: npx skills add https://github.com/cryptodiscolab/Crypto_Discovery_App --skill git-hygiene-clean-tree-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a strict protocol to prevent unwanted files like temporary files, secrets, and build artifacts from being committed to the Git repository, ensuring a clean and manageable codebase.

Core Features & Use Cases

Enforces Clean Tree Mandate: Prevents sensitive or unnecessary files from entering source control.
Manages Temporary Files: Guides the lifecycle of scratch scripts, ensuring they are deleted after use.
Pre-Push Validation: Ensures repository hygiene before every commit.
Use Case: Automatically identify and reject commits containing secrets or build outputs, maintaining the integrity of the project's history.

Quick Start

Run git status before pushing to ensure no unintended files are staged.

Frequently Asked Questions about Git Hygiene & Clean Tree Manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent secrets and temporary files from being committed to a Git repository?▼

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.

What is a clean Git tree mandate and when do I need it for repository management?▼

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.

How do I manage the lifecycle of scratch scripts in source control?▼

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.

Can I run pre-push validation to check repository hygiene before committing?▼

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.

Does this Git hygiene protocol work across multiple agents maintaining source control integrity?▼

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.

What are the limitations of automated Git hygiene for build artifacts and temporary files?▼

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.