メニュー
Git workflow helper. Use for committing changes, creating branches, viewing history, stashing work, resolving merge conflicts, and other git operations. Invoke when the user asks to commit, push, branch, stash, or do any git-related task.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | git |
| description | Git workflow helper. Use for committing changes, creating branches, viewing history, stashing work, resolving merge conflicts, and other git operations. Invoke when the user asks to commit, push, branch, stash, or do any git-related task. |
| allowed-tools | bash read |
Git workflow helper. Follow the instructions for the relevant operation.
When the user wants to commit changes:
Run all of these:
git status
git diff --cached
git diff
git log --oneline -5
If git diff --cached is empty but git diff shows changes, stage the relevant files:
git add <specific-files>
IMPORTANT: Do NOT run git add -A or git add . unless the user explicitly asked for all files. Stage specific files by name.
Do NOT stage files that look like secrets (.env, credentials.json, *.pem, etc.). Warn the user if you see them.
Rules:
If the project uses Conventional Commits:
<type>(<scope>): <short description>
git commit -m "<message>"
For multi-line messages, use heredoc:
git commit -m "$(cat <<'EOF'
<subject line>
<body>
EOF
)"
git log --oneline -1
Report what was committed.
When the user wants to create or switch branches:
git checkout -b <branch-name>
git checkout <branch-name>
git branch -a
git branch -d <branch-name>
Use -D only if the user explicitly asks to force-delete.
When the user wants to save work temporarily:
git stash push -m "<description>"
git stash list
git stash pop
git stash apply stash@{<n>}
When the user wants to see git history:
git log --oneline -20
git log --oneline -10 -- <file>
git show <commit-hash>
git blame <file>
When the user needs to resolve merge conflicts:
git status
Use read on each file listed as "both modified" to see the conflict markers.
Edit each file to remove conflict markers (<<<<<<<, =======, >>>>>>>) and keep the correct code.
git add <resolved-files>
git merge --continue
Or if rebasing:
git add <resolved-files>
git rebase --continue
When the user wants to push:
git push
If the branch has no upstream:
git push -u origin <branch-name>
IMPORTANT: Never force-push unless the user explicitly asks for it. If push is rejected, tell the user and suggest git pull --rebase first.
git reset --hard, git clean -f, or git push --force unless the user explicitly asksgit status before destructive operationsAnalyze the current git diff or staged changes for bugs, security issues, missing error handling, and breaking changes. Produces a structured review report. Use before committing or after making changes.
Start a dev server, take screenshots of the rendered frontend, and check for console errors. Use when you need to visually verify frontend changes, test styling, or check for runtime errors after editing frontend code.
Search the web and fetch page content. Use when you need external information like documentation, API references, error message lookups, or any information not available in the local codebase.