Braingit

Automate committing Markdown-only changes in a git repo with safe staging, ideal for note snapshots without affecting code or binaries.

Security Scan

The skill's requirements, instructions, and included script are consistent with its stated purpose of committing Markdown-only changes in a git repo and do not request unrelated credentials or perform network exfiltration.

Purpose & Capability

Name/description match the included script and documentation. The only code file implements staging and committing files matching a user-configurable glob (default *.md), which is exactly what the skill advertises.

Instruction Scope

SKILL.md and scripts operate only on a local git repository: they run git status, git add, and git commit. There are no network calls, external endpoints, or instructions to read unrelated system files. The pattern and repo path are configurable via documented env vars.

Install Mechanism

No install spec; this is an instruction-only skill with a small script included. Nothing is downloaded or written to disk by an installer.

Credentials

No credentials or special environment variables are required. The script accepts optional env vars (BRAINGIT_REPO, BRAINGIT_PATTERN, BRAINGIT_DRY_RUN) that are documented and directly related to its function.

Persistence & Privilege

The skill does not request always:true, does not modify other skills or global agent settings, and only makes local git commits (it does not push or store tokens). Autonomous invocation is enabled by default but is not combined with other risky behaviors.

Assessment

This skill appears to do what it says: locally stage and commit files matching a glob (default *.md). Before using it: (1) run with BRAINGIT_DRY_RUN=1 to verify which files would be staged; (2) double-check BRAINGIT_PATTERN and BRAINGIT_REPO so you don't accidentally stage more than intended (a broad pattern like '*' would stage everything); (3) avoid storing secrets in Markdown or explicitly exclude sensitive paths in .gitignore; (4) note the script commits locally only—it does not push to remotes or send data over the network. If you plan to run it automatically (cron/OpenClaw), test manual runs first and keep .gitignore tight.

Commit Markdown-only deltas in a git repository (typically a notes/workspace repo) using a deterministic script.

Article: https://github.com/gleb-urvanov/braingit/blob/master/braingit-article.md

Quick start

Commit Markdown changes (default: *.md)

From inside the target git repo:

./scripts/commit_md_changes.sh "md: snapshot"

Or specify a repo path:

BRAINGIT_REPO=/path/to/repo ./scripts/commit_md_changes.sh "md: snapshot"

Change what files are included

BRAINGIT_PATTERN='*.md' ./scripts/commit_md_changes.sh

Behavior

• Reads git status --porcelain -z
• Stages only matching files (default *.md)
• Commits only if something is staged
• Exits 0 when there is nothing to do

Scripts

• scripts/commit_md_changes.sh
  • Env:
    • BRAINGIT_REPO (default: cwd)
    • BRAINGIT_PATTERN (default: *.md)
    • BRAINGIT_DRY_RUN=1

References

• references/protocol.md — conventions + an OpenClaw cron example