skills.rest
JBODE-mhhs
JBODE-mhhsCOMMUNITY
Explore all skills by this author →
GitHub

local-version-control

Automate daily git snapshots of workspace changes with safety checks.

Updated Aug 27, 2026
Search Tags:#automation#git#commit#safety#pii#version-control#diff-review
One-click install
npx skills add https://github.com/JBODE-mhhs/Zeus2.0-public --skill local-version-control-jbode-mhhs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-version-control
Source: https://github.com/JBODE-mhhs/Zeus2.0-public/tree/main/templates/analyst/.claude/skills/local-version-control
Command: npx skills add https://github.com/JBODE-mhhs/Zeus2.0-public --skill local-version-control-jbode-mhhs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily snapshot of all agent workspace changes. Runs via auto-commit.sh with a two-layer safety review.

Core Features & Use Cases

  • Automated Snapshotting: Programmatically snapshot workspace changes and commit with descriptive messages.
  • Safety & Compliance: Blocks sensitive files and enforces size and type restrictions to prevent data leakage.
  • Use Case: Use during intensive development sprints to maintain an auditable history of changes across multiple agents.

Quick Start

Run auto-commit.sh to capture the next workspace snapshot and initiate a safe commit cycle.

Frequently Asked Questions about local-version-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate daily git snapshots of my agent workspace changes?▼

To automate daily git snapshots, run the auto-commit.sh script which stages workspace changes, reviews diffs for PII, and commits with descriptive messages without pushing.

How does the safety review work when committing automated git snapshots?▼

The safety review enforces a two-layer check that blocks sensitive files, reviews diffs for PII, and enforces size and type restrictions to prevent data leakage during the git commit cycle.

Can I use this automated git commit tool with multiple agents during a development sprint?▼

Yes, you can use this tool during intensive development sprints to maintain an auditable history of changes across multiple agents operating within the same workspace.

Do I need to enable a specific setting to run automated local version control?▼

Yes, you must set ecosystem.local_version_control.enabled to true in your config.json file before the automated git snapshot and commit cycle will operate.

Does the automated git commit script push changes to a remote repository?▼

No, the automated git snapshot script stages changes, reviews diffs, and commits with descriptive messages locally without pushing to a remote repository.

What is the best way to maintain an auditable history of workspace changes across missions?▼

The best way to maintain an auditable history is to run automated local version control daily, capturing workspace snapshots with safety checks that block sensitive files and prevent data leakage.

Related Skills

Explore More Software Engineering Skills→
jusjinukjusjinuk
1

onboard

Configure Slack tokens, environment files, and repository hooks for internbot deployment.

Community
Intermediate
0xRayAI0xRayAI

git-workflow

Automate Git branching, merging, and repository synchronization workflows.

Official
Intermediate
curtjencurtjen

no-sensitive-commits

Detect and prevent sensitive personal information in git commit messages.

Community
Basic
a-taka-tak
1

git-commit-push

Automates staging, committing, and pushing with standardized Git workflow.

Community
Basic