Braingit

What This Skill Does

Braingit is a specialized OpenClaw skill designed to streamline the version control process for documentation-heavy workflows. By automating the snapshotting of Markdown files within a Git repository, it eliminates the manual overhead of staging and committing individual changes. It functions by scanning the repository for files matching a specific pattern (defaulting to *.md), staging only those files, and executing a commit if changes are detected. This is particularly useful for users who maintain 'second brain' repositories, personal knowledge bases, or technical documentation hubs where they want to keep a granular, versioned history of their thoughts and edits without cluttering their commit logs with non-document files.

Installation

To integrate Braingit into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/gleb-urvanov/braingit

Use Cases

Braingit excels in several professional and personal scenarios. First, it is ideal for personal knowledge management (PKM) users who rely on Obsidian, Logseq, or other Markdown-based editors and want a 'set-it-and-forget-it' backup strategy. Second, it serves developers who maintain documentation repositories alongside their project code; by running a simple cron job or script via Braingit, they can ensure their technical documentation stays in sync with their logical progress without needing to manually run git commands after every paragraph update. Third, it is highly effective for teams using collaborative Markdown repositories where automated snapshots provide an audit trail of how project documentation has evolved over time.

Example Prompts

1. "OpenClaw, please run Braingit on my notes repository to snapshot all my current Markdown changes with the message 'daily update'."
2. "Use Braingit to stage only the changes in the /docs folder and commit them as a snapshot."
3. "Set up a recurring task to execute Braingit in my current directory every hour to ensure my documentation is always safely committed."

Tips & Limitations

To maximize the utility of Braingit, use the BRAINGIT_REPO environment variable to explicitly target your document directory if you are working from a parent folder. For safety, always utilize BRAINGIT_DRY_RUN=1 before running the command in production for the first time to verify which files are being picked up by the pattern matching. Be aware that Braingit is strictly additive; it will only stage files that match your BRAINGIT_PATTERN. It will not delete files or handle complex merge conflicts, so ensure your repository is in a clean state before relying on it for critical synchronization tasks. It is best used as an automated helper rather than a replacement for manual Git management in complex branches.