autocommit
Skill4 starsChanged 14 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jantichy/claudetheir own version, first seen Oct 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jantichy/claude★ 52same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository131 other files it gives its agents.
- agent-contractSkill
- brand-chrome-loginSkill
- contexto-aristasSkill
- crear-bot-nicoSkill
- daily-standupSkill
- design-a-grok-botSkill
- drift-hunt-rosterSkill
- explain-grokbotSkill
- exportar-botSkill
- govern-agentic-osSkill
- grok-bot-project-opsSkill
- hallazgoSkill
- handoff-local-hermesSkill
- identity-pipelineSkill
- loop-corpSkill
- no-devSkill
- orca-handoffSkill
- panorama-de-flujoSkill
- reporte-gmSkill
- routine-healthcheckSkill
- sprint-parallelSkill
- transcript-healthcheckSkill
- getting-started-brandySkill
- getting-started-calendario-contenidoSkill
- getting-started-cazador-de-canalesSkill
- getting-started-cazador-de-vuelosSkill
- getting-started-cazador-gangasSkill
- getting-started-cazador-inmobiliarioSkill
- getting-started-cazador-programasSkill
- getting-started-cazador-sponsorsSkill
- getting-started-cazador-viviendaSkill
- getting-started-content-drafterSkill
- getting-started-data-scienceSkill
- getting-started-demand-hunterSkill
- getting-started-digital-storesSkill
- getting-started-directory-builderSkill
- getting-started-enrichment-deskSkill
- getting-started-event-hunterSkill
- getting-started-expense-managerSkill
- getting-started-gm-operacionesSkill
- getting-started-inbox-managerSkill
- getting-started-intake-intelSkill
- getting-started-intelligence-gmSkill
- getting-started-join-a-startupSkill
- getting-started-last30daysSkill
- getting-started-life-opsSkill
- getting-started-luma-taggingSkill
- getting-started-market-watcherSkill
- getting-started-meta-vaultSkill
- getting-started-musa-designerSkill
- getting-started-plantillas-notionSkill
- getting-started-product-hunterSkill
- getting-started-publisherSkill
- getting-started-pulso-brandSkill
- getting-started-pulso-diaSkill
- getting-started-renewals-hunterSkill
- getting-started-saves-archivistSkill
- getting-started-scraping-deskSkill
- getting-started-seo-deskSkill
- getting-started-sliderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Do not use this skill for normal manual git workflows.
- Distinctive: line 29
Run from repo root:
- Very specific: line 65
After starting, verify again with status.
- Distinctive: line 100
if not healthy, the most likely reason
- Distinctive: line 104
Do not restart blindly if the user is in the middle of sensitive git operations.
- Distinctive: line 105
Do not hide when the daemon is flaky.
- Distinctive: line 106
Treat nested repos and unrelated git states carefully.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 restartStandard Workflow
1. Check Status First
Always start with:
bash .scripts/auto-commit-control.sh statusIf running, report:
- running/not running
- whether the user actually wants a change
2. If Starting
Before starting, verify:
fswatchexists- there is no obvious git operation in progress
Then run:
bash .scripts/auto-commit-control.sh startAfter starting, verify again with status.
3. If It Fails
Check:
tail -n 80 .scripts/.auto-commit.logThen 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:
fswatchmissing- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

