メニュー
Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Restore claude/codex agents from a tmux-reboot snapshot after tmux-resurrect reopens their windows.
Snapshot running tmux claude/codex agents immediately before a reboot so their sessions can be restored afterward.
Commit changes, run git-test precommit checks, and fix failures. Use when asked to fix build, test, lint, typecheck, or precommit failures.
Running precommit checks and build validation. ALWAYS use after ANY code changes.
This skill should be used after completing any task, before returning control to the user. Always run this skill — it handles the case where there's nothing to do.
Coordination guidelines for leading a team of task-executing agents
| name | git-workflow |
| description | Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message. |
This skill provides guidelines for git operations including commits, conflict resolution, and branch management.
Use the git-commit skill for commit operations. In Claude Code this may delegate to the git:commit-handler agent; in Codex, follow the git-commit skill directly unless the user explicitly asks for a subagent workflow.
Every commit message is a single line — no body, no bullet list, no blank-line-separated paragraphs. It must:
A task description or prompt is intent, not the message. When the prompt is long or multi-line, distill it to one line — never copy it verbatim into the commit message. This rule applies to writing new commits and to rewording existing ones with git history reword.
Use the git-conflicts skill to resolve git merge or rebase conflicts. In Codex, spawn a subagent only when the user explicitly asks for subagents or parallel agent work.
Use the git-rebase skill to rebase the current branch on upstream.
Use newer git commands instead of their legacy equivalents whenever possible:
git switch instead of git checkout for switching branchesgit switch -c instead of git checkout -b for creating branchesgit restore instead of git checkout -- for restoring filesgit restore --staged instead of git reset HEAD for unstaging filesgit replay --onto instead of git rebase --onto for non-interactive onto rebasesgit history reword instead of interactive rebase or amending for editing commit messagesgit history split instead of interactive rebase for splitting commits