Menü
Use for any git operation — branching, merging, rebasing, conflict resolution, or understanding git state. Defines safety rules for destructive commands.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
System design and architecture decisions. Use when planning new features, evaluating trade-offs, or designing how components should connect. Proposes 2-3 approaches and recommends one.
Smart commit workflow. Reviews staged changes, writes conventional commit messages, and catches issues before committing. Use when ready to commit work.
Quality review of completed work. Use after making changes and before claiming completion. Reviews code for correctness, edge cases, security, and maintainability.
Systematic debugging workflow. Use when diagnosing bugs, test failures, or unexpected behavior. Follows a rigorous reproduce → isolate → hypothesize → fix → verify cycle.
Systematic multi-agent research. Use when you need to deeply investigate a topic, codebase, or question by spawning parallel research agents and synthesizing their findings.
Deep code explanation. Use when you need to understand or explain how a system, module, or function works. Traces data flow, maps dependencies, and explains design decisions.
| name | git-workflow |
| description | Use for any git operation — branching, merging, rebasing, conflict resolution, or understanding git state. Defines safety rules for destructive commands. |
You handle all git operations with extreme care. Git mistakes can lose work.
NEVER without explicit user request:
push --force, reset --hard, checkout ., restore ., clean -f, branch -D--no-verify, --no-gpg-signALWAYS:
git add -A or git add .)git status and git diff before committingWhen asked to commit:
Assess (in parallel):
git status — see untracked and modified filesgit diff and git diff --staged — see actual changesgit log --oneline -5 — recent commit styleDraft message:
feat:, fix:, refactor:, etc.Stage and commit:
.env, credentials)If pre-commit hook fails:
When asked to create a PR:
Assess (in parallel):
git status — untracked filesgit diff — uncommitted changesgit log base..HEAD — all commits in the branchCreate PR:
-u flag if neededgh pr create