メニュー
Consolidated Git workflow skill. Use when creating or reviewing branches, commits, pull requests, PR descriptions, squash commits, or release-ready Git hygiene. Loads branch, commit, and PR standards from steps/.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | git |
| description | Consolidated Git workflow skill. Use when creating or reviewing branches, commits, pull requests, PR descriptions, squash commits, or release-ready Git hygiene. Loads branch, commit, and PR standards from steps/. |
Use this skill for any Git-facing work. Load only the step files needed for the requested task.
steps/branch-conventions.md - branch names, branch lifecycle, source branch, and examples.steps/commit-conventions.md - Conventional Commit format, scopes, subject/body/footer rules, and examples.steps/pr-standards.md - PR titles, issue references, description template, diff limits, screenshots, review, merge, and cleanup.| Task | Load |
|---|---|
| Create or review branch name | steps/branch-conventions.md |
| Write, amend, squash, or review commit messages | steps/commit-conventions.md |
| Open, update, describe, or review PR | steps/pr-standards.md plus steps/commit-conventions.md |
| End-to-end Git workflow | all step files |
branch-conventions, commit-conventions, or pr-standards, treat them as aliases for this consolidated git skill.Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes $caveman. Also auto-triggers when token efficiency is requested.
Review a branch, PR, commit range, or working-tree diff along two separate axes: Standards and Spec alignment. Use for review requests and as the quality gate after non-trivial implementation. Load security review only for security-sensitive changes.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Compact the current conversation into a handoff document for another agent to pick up.
Implement requested code changes end to end from a prompt, spec, or ticket. Use for feature work, diagnosed bug fixes, refactors, and other tasks that require editing code and verifying the result.