メニュー
Use before git mutation, branch deletion, resets, cleaning, force pushes, broad restore commands, PR operations, or any git action with destructive or remote side effects.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when writing technical articles, blog posts, X/Twitter threads, LinkedIn posts, documentation, runbooks, or any text that must sound like a specific person, not a generic assistant. Also use when the user asks to humanize text, remove AI-sounding language, rewrite in their voice, or convert rough notes into publishable content. Trigger even when the user just says "write this up" or "draft a post about X" without explicitly mentioning voice or tone.
Use when reviewing architecture, planning refactors, reducing coupling, improving testability, or deciding whether modules should become deeper behind simpler interfaces.
Use when the user asks for caveman mode, terse mode, fewer tokens, less prose, or very brief technical communication.
Use for hard bugs, failing checks, pipeline failures, homelab incidents, performance regressions, or reports that something is broken and needs root-cause analysis.
Use when a plan, design, or implementation request has ambiguity that could change scope, architecture, acceptance criteria, safety, or validation.
Use when work should continue in another session, another lane, or a fresh context window, especially after planning, debugging, or partial implementation.
| name | git-guardrails |
| description | Use before git mutation, branch deletion, resets, cleaning, force pushes, broad restore commands, PR operations, or any git action with destructive or remote side effects. |
Use prompt and permission safety. Do not add hook scripts unless the user explicitly asks.
git status --shortgit diffgit diff --cachedgit log --oneline -n 15 when history mattersgit pushgit reset --hardgit clean -f or strongergit branch -Dgit checkout . or broad git restore .Commit only when the user explicitly asks. If committing, use repository style and do not bypass hooks.
State the intended git action, the evidence inspected, and the safety decision: proceed, ask, or block.