AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Autocommit

skill-theveller-claude-skills-autocommit · by TheVeller

Operate the local auto-commit daemon for this vault. Use when the user wants to start, stop, restart, inspect, debug, or verify the auto-commit system, or asks about background git automation in this workspace.

↗ Repository
— No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-theveller-claude-skills-autocommit

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-theveller-claude-skills-autocommit)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 25d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Autocommit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Autocommit

Manage the vault's local auto-commit system safely and consistently.

This skill is for the modular daemon behind:

  • .scripts/auto-commit-control.sh
  • .scripts/auto-commit.sh
  • .scripts/auto-commit/

Use This Skill For

  • starting the auto-commit monitor
  • stopping it
  • restarting it
  • checking status
  • reading recent logs
  • understanding why it is not committing or not staying alive

Do not use this skill for normal manual git workflows. This is specifically for the background daemon.

Core Commands

Run from repo root:

bash .scripts/auto-commit-control.sh start
bash .scripts/auto-commit-control.sh stop
bash .scripts/auto-commit-control.sh status
bash .scripts/auto-commit-control.sh logs
bash .scripts/auto-commit-control.sh restart

Standard Workflow

1. Check Status First

Always start with:

bash .scripts/auto-commit-control.sh status

If running, report:

  • running/not running
  • whether the user actually wants a change

2. If Starting

Before starting, verify:

  • fswatch exists
  • there is no obvious git operation in progress

Then run:

bash .scripts/auto-commit-control.sh start

After starting, verify again with status.

3. If It Fails

Check:

tail -n 80 .scripts/.auto-commit.log

Then inspect:

  • .scripts/auto-commit-control.sh
  • .scripts/auto-commit.sh
  • .scripts/auto-commit/core/monitor.sh
  • .scripts/auto-commit/integrations/obsidian-detector.sh

Key failure patterns:

  • fswatch missing
  • process starts but dies immediately
  • Obsidian Git conflict heuristics skipping too aggressively
  • commit generation failing
  • push failing while commit succeeds

4. If Reviewing Behavior

Useful references:

  • 06_Metadata/Tools/Misc/Auto-Commit-System.md
  • .scripts/auto-commit/README.md

Reporting Back

When done, report:

  • current daemon state
  • what command was run
  • whether it is now healthy
  • if not healthy, the most likely reason

Safety

  • Do not restart blindly if the user is in the middle of sensitive git operations.
  • Do not hide when the daemon is flaky; say whether it truly stayed running.
  • Treat nested repos and unrelated git states carefully.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Security