How do I install the Git Ops skill?

Run npx skillmds@latest add alexsmedile/git-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Ops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Ops?

alexsmedile (@alexsmedile) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Ops by alexsmedile — Agent Skill

Name: Git Ops
Author: alexsmedile

Git Ops

Focused execution and postcondition validation engine for Git & GitHub operations (commit, push, branch, worktree, merge, rebase, PR, tag, release). Invoked by repo-governance or in pre-verified contexts.

alexsmedile 8a87e6b 17 files · 116.0 KB Updated Sep 17, 2026

File contents

git-ops

Execute selected operations with local judgment and postcondition verification. Native git/gh are default; use git-stack.sh for compact fast-paths.

Entry & Routing

Entry: Accepts pre-verified repository boundaries or handoffs from repo-governance. General conversational requests enter via repo-governance.
Halt Condition: If uncommitted collisions, divergence, or interrupted markers appear, halt immediately and route to governance recover.

Operation Fast Paths

GIT_STACK="${CLAUDE_SKILL_DIR:-<skill-dir>}/scripts/git-stack.sh"
bash "$GIT_STACK" commit   # exit 0: CLEAN, 1: BLOCKED, 2: NOTHING_TO_DO
bash "$GIT_STACK" push     # check upstream and remote freshness
bash "$GIT_STACK" tag --version 1.2.3
bash "$GIT_STACK" scan     # conventional commit scan since last tag

Operation	Pre-conditions	Execution & Script Path	Post-condition Verify
`commit`	Feature branch, clean index, `.gitignore` present	`git-stack.sh commit --execute --message "..."`	Commit created; report residual unstaged count
`push`	Upstream tracked, no divergence	`git-stack.sh push --execute` (force-push blocked)	Remote ref equals local HEAD
`merge`	Target branch checked, clean working tree	`--ff-only` for linear stacks; `--no-ff` for true branches	Target contains source; offer `git branch -d` on subsumed branches
`tag/release`	Clean release branch, manifests aligned	`git-stack.sh tag --version X.Y.Z`	Annotated tag matches HEAD; GitHub release if requested

Report Format

Emit one left-border box inside a fenced text block upon completion:

┌─ COMMITTED · feat/login · 3 files
│ commit   a1b2c3d  feat: add password reset flow
│ files    3 changed, +82 -14
│ next     push when requested
└─

Hard Guardrails

History Protection: Preserve shared history. Rewrite only PRIVATE or authorized PUBLISHED_SOLO with lease protection.
Stage Discipline: Stage only named/approved paths. Commit runner checks secrets and large files.
Secret Containment: Revoke/rotate exposed keys before history surgery.
Merge Integrity: Integrate feature branch -> verify tests -> advance default branch. Never resolve conflicts directly on default branch.

---name: git-opsdescription: Focused execution and postcondition validation engine for Git & GitHub operations (commit, push, branch, worktree, merge, rebase, PR, tag, release). Invoked by repo-governance or in pre-verified contexts.---# git-opsExecute selected operations with local judgment and postcondition verification. Native `git`/`gh` are default; use `git-stack.sh` for compact fast-paths.## Entry & Routing- **Entry**: Accepts pre-verified repository boundaries or handoffs from `repo-governance`. General conversational requests enter via `repo-governance`.- **Halt Condition**: If uncommitted collisions, divergence, or interrupted markers appear, halt immediately and route to governance `recover`.## Operation Fast Paths```bashGIT_STACK="${CLAUDE_SKILL_DIR:-<skill-dir>}/scripts/git-stack.sh"bash "$GIT_STACK" commit # exit 0: CLEAN, 1: BLOCKED, 2: NOTHING_TO_DObash "$GIT_STACK" push # check upstream and remote freshnessbash "$GIT_STACK" tag --version 1.2.3bash "$GIT_STACK" scan # conventional commit scan since last tag```| Operation | Pre-conditions | Execution & Script Path | Post-condition Verify ||---|---|---|---|| `commit` | Feature branch, clean index, `.gitignore` present | `git-stack.sh commit --execute --message "..."` | Commit created; report residual unstaged count || `push` | Upstream tracked, no divergence | `git-stack.sh push --execute` (force-push blocked) | Remote ref equals local HEAD || `merge` | Target branch checked, clean working tree | `--ff-only` for linear stacks; `--no-ff` for true branches | Target contains source; offer `git branch -d` on subsumed branches || `tag/release` | Clean release branch, manifests aligned | `git-stack.sh tag --version X.Y.Z` | Annotated tag matches HEAD; GitHub release if requested |## Report FormatEmit one left-border box inside a fenced `text` block upon completion:```text┌─ COMMITTED · feat/login · 3 files│ commit a1b2c3d feat: add password reset flow│ files 3 changed, +82 -14│ next push when requested└─```## Hard Guardrails- **History Protection**: Preserve shared history. Rewrite only `PRIVATE` or authorized `PUBLISHED_SOLO` with lease protection.- **Stage Discipline**: Stage only named/approved paths. Commit runner checks secrets and large files.- **Secret Containment**: Revoke/rotate exposed keys before history surgery.- **Merge Integrity**: Integrate feature branch -> verify tests -> advance default branch. Never resolve conflicts directly on default branch.

Frequently asked questions