Working Tree Governor

Govern dirty git working trees by classifying runtime noise vs real source changes, defaulting to selective staging, verifying staged scope, and asking the o...

This skill appears to do what it says: help you selectively stage and commit while avoiding runtime noise. Before installing, do the following: - Confirm git is available on the agent host (SKILL.md runs git but metadata does not declare it). Add 'git' to the required binaries if you manage the registry entry. - Review and adapt the pattern lists and heuristics to your repository (the examples mention project-specific paths like 'hermes' and 'shared/*'); otherwise the skill may misclassify important files. - Keep the operator-approval gate enforced; test the skill in a disposable repository first to observe behavior. Ensure the agent cannot auto-commit or run without your interactive approval if you require stricter control. - Because this is instruction-only, it will execute the git commands shown — ensure the agent's runtime user has appropriate repository access but not elevated system privileges. - If you want stricter safety, restrict autonomous invocation of this skill at the platform/policy level, or require an explicit manual confirmation step before any git add/commit is executed.

Type: OpenClaw Skill Name: working-tree-governor Version: 1.0.0 The working-tree-governor skill is a utility designed to help an AI agent manage git repositories by distinguishing between source code and runtime artifacts like logs, caches, and state files. It implements a structured workflow using standard git commands (e.g., git status, git diff, git add) and enforces selective staging to prevent repository pollution. The instructions in SKILL.md prioritize operator approval and safety, with no evidence of data exfiltration, malicious execution, or harmful prompt injection.