| name | git-workflow |
| description | Git workflow rules for Renfield. Commit message format, issue numbering, branch naming, PR creation, documentation updates before push. Triggers on "commit", "push", "PR erstellen", "pull request", "branch", "git", "merge". Use when this capability is needed. |
| metadata | {"author":"ebongard"} |
Git Workflow
CRITICAL RULES
- NIEMALS ohne Erlaubnis pushen —
git push NUR nach expliziter Bestätigung
- Issue-Nummer bei jedem Commit — Vor jedem Commit nach der Issue-Nummer fragen
- Dokumentation vor Push — CLAUDE.md, docs/, README müssen Änderungen widerspiegeln
- Branch Protection — Direct push to
main is blocked. Always use feature branch → PR → merge.
- Co-Authored-By — Jeder Commit muss die Co-Author-Zeile enthalten
Commit Message Format
type(scope): Kurze Beschreibung (#issue)
Längere Beschreibung falls nötig.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Example: feat(satellites): Add monitoring dashboard (#25)
Commit Types
| Type | Usage |
|---|
feat | Neues Feature |
fix | Bugfix |
docs | Dokumentation |
refactor | Code-Refactoring |
test | Tests hinzufügen/ändern |
chore | Wartung, Dependencies |
Workflow
- Create feature branch:
git checkout -b type/short-description
- Make changes + write tests (TDD)
- Update documentation (CLAUDE.md, docs/)
- Ask for issue number
- Commit with proper format
- Ask user: "Soll ich pushen?"
- Only after confirmation:
git push -u origin branch-name
- Create PR:
gh pr create --title "type(scope): Description (#issue)" --body "..."
PR Format
gh pr create --title "type(scope): Description (#issue)" --body "$(cat <<'EOF'
## Summary
- Bullet points describing changes
## Test plan
- [ ] Tests added/updated
- [ ] Manual testing done
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
Source: ebongard/renfield — distributed by TomeVault.
