autogit-ops

autogit ops

This skill ships inside the autogit plugin. This file lives at <plugin-root>/skills/autogit-ops/SKILL.md, so the bundled zero-dependency CLI is two directories up: <plugin-root>/index.js. Resolve <plugin-root> from this file's own absolute path. Never assume a global autogit binary — always run the bundled one:

node "<plugin-root>/index.js" <subcommand>

Run it from the repo the user means (their project directory, not the plugin directory).

Dispatch

Argument	Run	Notes
on	node .../index.js on	Enables auto-push for this repo (writes .git/autogit.json). After it succeeds, tell the user this repo is now opted in — every turn ends with stage → secrets scan → commit → push once autogit's lifecycle hooks are wired for the agent you're running. As a plugin, autogit wires those hooks itself on Claude Code, Codex, Cursor, and Factory Droid, so there on is all that's needed — except on Codex, which treats plugin hooks as non-managed and skips them until the user runs /hooks inside Codex and trusts autogit once (re-prompted whenever the hook file changes); tell Codex users to do that or they'll see no automatic commits. Gemini gets this skill but not the plugin's auto-ship hook (a harness limitation — see the plugin's docs/gemini.md), so on Gemini automatic shipping needs a one-time autogit setup (node .../index.js setup) or manual ship. quiet and pr config keys go in .git/autogit.json.
off	node .../index.js off	Disables auto-push for this repo.
status (default)	node .../index.js status	Also the no-args behavior. Surface pending batches and failed-push lines prominently if present.
undo	node .../index.js undo	Rewinds the last autogit commit on the remote and locally; changes return uncommitted. Repeatable. It refuses non-autogit commits on its own — no extra confirmation needed.
ship	node .../index.js ship	Ship right now (stage → scan → commit → push).
flush	node .../index.js ship --flush	Ship a pending quiet batch immediately.
dry-run	node .../index.js ship --dry-run	Report what would ship; commits nothing. Note: like ship, it runs git add -A + git reset, clearing any manual staging selection.

Behavior notes

• All human-readable output is on stderr; exit 0 = success or clean no-op, exit 1 = real failure. Relay the CLI's own message to the user rather than paraphrasing loosely.
• If node is missing from PATH, say so — the plugin's automatic hooks silently no-op without Node, so nothing has been shipping.
• Automatic ship-after-every-turn depends on autogit's lifecycle hooks being wired for the running agent. The plugin wires them itself on Claude Code, Codex, Cursor, and Factory Droid, so on those on per repo is all that's needed (the non-Claude wiring is conformant to each harness's docs but hasn't been run end-to-end — if a turn doesn't ship, that's the place to check). On Gemini the plugin exposes this skill but cannot wire auto-ship (a harness limitation, see docs/gemini.md), so there automatic shipping needs autogit setup or a manual ship.
• If the user asks for anything else (custom commit message, force past a secrets block), the flags are -m "msg" and --force-secrets on ship.