Skip to content
Agentmart
Submit a tool

git-workflow-guardian

Enforce correct git workflow: never push main directly, use feature branches + PR, respect repo-specific branch taxonomy and ALFRED/BRGS guards.

Skill by gerivdb

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/gerivdb-git-workflow-guardian

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Enforce correct git workflow: never push main directly, use feature branches + PR, respect repo-specific branch taxonomy and ALFRED/BRGS guards. Use before any git push or branch creation.

Use cases: productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/git-workflow-guardian

What's inside

Skill name
git-workflow-guardian
Description
Enforce correct git workflow: never push main directly, use feature branches + PR, respect repo-specific branch taxonomy and ALFRED/BRGS guards. Use before any git push or branch creation.
License
MIT
Instructions
100 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# git-workflow-guardian

> **IntentHash**: `0xGIT_WORKFLOW_GUARDIAN_20260912`  
> **Version**: 1.0.0  
> **Domain**: transverse  
> **Scope**: tous les repos `D:\DO\WEB\TOOLS\*` et `C:\DevTools`

---

## Objectif

Verrouiller le workflow git pour **ne plus jamais** :
- pusher directement sur `main`
- créer une branche sans préfixe autorisé
- ignorer les guards locaux (`ALFRED`, `BRGS`)
- oublier la logique `feat -> push -> PR -> merge`

---

## Protocole obligatoire

### Avant tout `git push`

1. Lire `git branch --show-current`
2. Si branche = `main` → **STOP**, créer d'abord une branche de feature
3. Vérifier le préfixe de branche via `branch-taxonomy-enforcer`
4. Vérifier les chemins modifiés via `pre-push-path-audit`
5. Si tous les checks passent → `git push origin <branche>`
6. Créer la PR via KIVA-CLI / ECOS-CLI (interdiction `gh pr` en BDCP)

### Logique feature branch correcte

```powershell
# 1. Rester sur main a jour
git checkout main
git pull origin main

# 2. Creer une branche de feature
git checkout -b feat/<slug>-<id>

# 3. Committer les changements
git add <fichiers>
git commit -m "feat(<scope>): <desc>"

# 4. Pousser la branche
git push origin feat/<slug>-<id>

# 5. Creer la PR via KIVA-CLI
python -m kiva.cli pr create --title "..." --body "..."
```

### En cas de commits déjà sur main (comme aujourd'hui)

1. **Ne pas push** : `git push origin main` est interdit par ALFRED
2. **Créer une branche depuis main** : `git checkout -b feat/<slug>-<id>`
3. **Reset main** sur `origin/main` : `git checkout main && git reset --hard origin/main`
4. **Re-appliquer les changements** sur la branche feat
5. **Pousser la branche** et créer la PR

---

## Guards transversaux

| Guard | Action |
|-------|--------|
| **ALFRED** | Bloque le push direct sur `main` → utiliser une branche feat |
| **BRGS** | Vérifie le préfixe de branche → utiliser `feat/`, `fix/`, `docs/`, `chore/`, `refactor/` |
| **Taxonomie unifiée** | Format `type/jurisdiction-slug-id` → ex: `feat/env2-lxc-network-001` |
| **BDCP** | Interdit `gh pr` → utiliser KIVA-CLI / ECOS-CLI uniquement |

---

## Anti-patterns bloquants

- `git push origin main` → **INTERDIT** (ALFRED BLOCK)
- Créer une branche `docs/curx-...` en contournement → **INTERDIT** (taxonomie non conforme)
- Commiter sur `main` puis push → **INTERDIT** (workflow inverse)
- Utiliser `gh pr create` → **INTERDIT** (BDCP)
- Ignorer les guards locaux → **INTERDIT**

---

## Checklist avant push

- [ ] Branche actuelle ≠ `main` ?
- [ ] Préfixe de branche autorisé (`feat/`, `fix/`, `docs/`, `chore/`, `refactor/`) ?
- [ ] Format taxonomie respecté (`type/jurisdiction-slug-id`) ?
- [ ] `pre-push-path-audit` passé ?
- [ ] PR créée via KIVA-CLI / ECOS-CLI (pas `gh`) ?

---

## Référence ADR

- **ADR** : ADR-2026-06-07-001-ADR-GOVERNANCE-GATE
- **IntentHash** : `0xADR_GOVERNANCE_GATE_20260607`
- **Dépôt** : gerivdb/GOVERNANCE-HUB
- **Statut ADR** : proposed

From gerivdb/SKILLS, MIT.

More from gerivdb/SKILLS

Signals

Stars
1
Forks
0
Open issues
8
Last commit (this folder)
Sep 12, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from gerivdb

Cite this page

git-workflow-guardian skill. Agent Mart. https://agentmart.dev/skills/gerivdb-git-workflow-guardian (last updated 2026-10-24)