Config Tracker

What This Skill Does

The Config Tracker skill, developed by altaircardinal, serves as an automated version control system integrated directly into your OpenClaw environment. It monitors critical configuration and agent-definition files for changes, automatically committing updates to a local Git repository. By hooking into the before_prompt_build process, it ensures that your workspace state—including identity files, memory logs, and tool configurations—is always preserved and trackable. This creates a safety net for your AI agent's evolution, allowing you to audit how your agent's personality, behavior, and tools have changed over time without needing to manage Git commands manually.

Installation

To install this skill, use the ClawHub CLI command: clawhub install openclaw/skills/skills/altaircardinal/config-tracker Alternatively, you can manually clone the repository into your OpenClaw skills directory. After placing the files in /Volumes/File/OpenClaw/workspace/skills/, restart your OpenClaw gateway. The skill will automatically detect the presence of configuration files and initialize a Git repository on the first run to begin tracking your workspace metadata.

Use Cases

• Agent Evolution Tracking: Review how SOUL.md or IDENTITY.md has shifted over time as you provide feedback to your agent.
• Configuration Recovery: Accidentally broke your agent's functionality? Use the generated commit history to revert your openclaw.json or TOOLS.md to a known stable state.
• Team Transparency: When multiple users or agents modify a shared workspace, this tool maintains a clear audit trail of who changed which settings and when.

Example Prompts

1. "OpenClaw, can you list the recent changes made to my SOUL.md file using the Config Tracker history?"
2. "Show me the last three commits in the config repository to see what was modified in TOOLS.md today."
3. "Please revert the IDENTITY.md file to the version from yesterday using the tracking history."

Tips & Limitations

• Frequency: The skill includes a 5-second commit cooldown to prevent excessive disk I/O, but frequent automated edits (like those from the Doctor skill) will still generate a dense commit history. Use git log periodically to clean up or squash commits.
• Storage: Since every change creates a new commit, your Git repository may grow over time. Monitor your workspace storage periodically if you have a massive amount of configuration files.
• Visibility: Ensure that your environment has Git installed and configured, as the skill relies on the local system's git binary to perform repository operations.