git-guard
v1.2.0The /git-commit and /git-push skills — the sanctioned path through git-guard's shell wrapper + PreToolUse hook + deny rules. Each walks its own stages with explicit confirmation at every step; push always requires its own separate confirmation. The same PreToolUse hook also enforces the GitFlow (Lite) branch-naming convention on branch creation (git checkout -b / git switch -c / git branch <name>).
By Mark SusolLicense: MIT1 GitHub starsUpdated 3 days ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Oct 4, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install git-guard for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install git-guard-2@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/msusol/claude-code-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is git-guard/plugins/git-guard/.
Plugin files
├── .claude-plugin/plugin.json├── skills/git-commit/SKILL.md└── skills/git-push/SKILL.md
Included Skills2
Use this skill whenever the user wants to commit changes, stage files, or save work to git. Trigger on: /git-commit, "commit my changes", "stage and commit", "save my work", "make a commit", "commit these changes", or any request to create a git commit. This is the ONLY sanctioned path for git commit/tag operations — it bypasses the shell wrapper that blocks unguided calls, because it enforces explicit per-step confirmation. Does NOT push — pushing is a separate action; use the git-push skill for that.
Use this skill whenever the user wants to push commits to a remote. Trigger on: /git-push, "push this", "push my changes", "push to origin", "push the commit(s)", or any request to push. This is the ONLY sanctioned path for git push — it bypasses the shell wrapper that blocks unguided push calls, because it enforces explicit confirmation for every single push. It does NOT commit — if there is nothing to push yet (no local commits ahead of the remote), tell the user to use the git-commit skill first.
Plugin manifests1
{
"name": "git-guard",
"version": "1.2.0",
"description": "The /git-commit and /git-push skills — the sanctioned path through git-guard's shell wrapper + PreToolUse hook + deny rules. Each walks its own stages with explicit confirmation at every step; push always requires its own separate confirmation. The same PreToolUse hook also enforces the GitFlow (Lite) branch-naming convention on branch creation (git checkout -b / git switch -c / git branch <name>).",
"author": {
"name": "Mark Susol"
},
"license": "MIT"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[git-guard on Agent Plugins Marketplace](https://pluginsmp.com/plugins/git-guard-2)