自动追踪并自动提交 OpenClaw 配置和关键工作区 markdown 文件的变更，无需手动操作。

This skill does roughly what it says — auto-detecting and committing changes to OpenClaw config and specified workspace markdown files — but take precautions before installing: - Inspect the full source (you've got it) to confirm there is no 'git push' or remote upload behavior in the truncated portion; if you want, provide the remaining code to re-check. The visible code does not perform network exfiltration. - Ensure git is installed and that you are comfortable with the plugin creating .git repositories in your workspace and ~/.openclaw (it will initialize repos and create commits). - Review which files will be tracked. If any tracked files may contain secrets (API keys, tokens, passwords), either remove them from the tracked list or add them to a local .gitignore before enabling the skill. - Check for existing git remotes in those directories. If a remote is configured, commits could be pushed later (by other tools or manual action); consider removing remotes or ensuring they point to a private destination. - If you want more assurance, run the plugin in an isolated environment or disable it (set enabled=false) until you're confident. Also ask the maintainer to declare 'git' as a required binary in the metadata and to fix the metadata that called this 'instruction-only'. If you want, I can: (a) search the truncated portion for 'push'/'remote' or other network calls if you paste it; (b) suggest a safe .gitignore and configuration to avoid committing secrets; or (c) produce a minimal checklist to harden installation.

Type: OpenClaw Skill Name: config-tracker Version: 1.0.2 The skill is a utility designed to provide automated version control for OpenClaw configuration and workspace files. It uses local Git commands via `node:child_process` to track and commit changes to files such as `openclaw.json`, `MEMORY.md`, and `USER.md` whenever a dialogue turn begins. The code is transparent, lacks network exfiltration capabilities, and strictly performs local `git add` and `git commit` operations without any `git push` or remote execution logic.