
Git Guardrails
- Updated June 17, 2026
- l3ocho/mktpl-claude-datasaas
git-guardrails provides pre-commit safety hooks that validate branch names and commit messages before they land. Teams use it to enforce consistent git conventions and prevent bad branches or messages from entering history.
Key points
- Branch-name safety hooks
- Commit-message validation
- Pre-commit enforcement
Git Guardrails by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add l3ocho/mktpl-claude-datasaas/plugin install git-guardrails@mktpl-claude-datasaasAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | June 17, 2026 |
|---|---|
| Repository | l3ocho/mktpl-claude-datasaas ↗ |
What it does
Pre-commit hooks that enforce branch-name and commit-message conventions to keep git history safe and consistent.
README.md
git-guardrails
Two PreToolUse(Bash) safety hooks, nothing else:
| Hook | Blocks when | Fix |
|---|---|---|
branch-check.sh |
Branch-creation commands (git checkout -b, git switch -c, git branch <name>) use an unrecognized prefix or forbidden characters |
Use <type>/<description> where type is feat|fix|chore|docs|refactor|test|perf|debug, or claude/... for Claude Code on the web |
commit-msg-check.sh |
git commit -m "..." message is not Conventional Commits |
Use <type>(<scope>)?!?: <description> |
Why this exists
The retired git-flow plugin bundled a large set of commands that reimplemented things Claude Code now does natively through plain Bash. The two hooks were the only parts pulling their weight, so they live here as a hook-only plugin.
Bypass
Don't. If a hook blocks you, fix the branch name / commit message. Never use --no-verify.
Files
git-guardrails/
├── .claude-plugin/
│ ├── plugin.json
│ └── metadata.json
└── hooks/
├── hooks.json
├── branch-check.sh
└── commit-msg-check.sh