メニュー
Show the configured kill phrases and case sensitivity for both local (project) and global (user) terminator installations. Use when the user asks "what is my kill phrase", "show terminator config", "terminator info", or "what phrase is configured".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | terminator:info |
| description | Show the configured kill phrases and case sensitivity for both local (project) and global (user) terminator installations. Use when the user asks "what is my kill phrase", "show terminator config", "terminator info", or "what phrase is configured". |
| disable-model-invocation | false |
Show the currently configured kill phrases for local and/or global scope.
local_config=".claude/terminator.json"
global_config="$HOME/.claude/terminator.json"
echo "=== LOCAL scope ($local_config) ==="
if [ -f "$local_config" ]; then
cat "$local_config"
else
echo "not installed"
fi
echo ""
echo "=== GLOBAL scope ($global_config) ==="
if [ -f "$global_config" ]; then
cat "$global_config"
else
echo "not installed"
fi
Present the findings clearly:
## Terminator Info
LOCAL scope (.claude/terminator.json):
single_killphrase : <phrase or "not set">
double_killphrase : <phrase or "not set">
case sensitive : <true|false|"not set">
GLOBAL scope (~/.claude/terminator.json):
single_killphrase : <phrase or "not set">
double_killphrase : <phrase or "not set">
case sensitive : <true|false|"not set">
If a scope is not installed, show — not installed — for that block.
If neither scope is installed, offer /terminator:install.
This skill should be used when the user asks to "check clean code", "review code cleanliness", "find code smells", "is this function too long", "are these names clear", "review my error handling", "check my tests", or "clean up this code". Also triggers when the user mentions Clean Code, Uncle Bob, Robert Martin, meaningful names, function length, comment rot, F.I.R.S.T. tests, or names a dimension directly ("naming", "boundaries", "concurrency"). Supports auditing all nine dimensions at once or focusing on a single dimension.
Scan Claude Code chat session logs for recurring agent anti-patterns (hedging, stalling, skipping, false completions, preference-asking, dismissing, cosmetic, caveats, flagging) and produce a ranked report with frequency counts, example excerpts, and suggested guardrail rules. Use when user asks to "analyze sessions for anti-patterns", "find bad patterns in logs", "what anti-patterns am I seeing", "agent-guardrails analyze", or wants data-driven guardrail recommendations.
Install agent behavioral guardrail rules into a project's .claude/ directory. Generates a Stop hook bash script and configures settings.local.json. Includes nine battle-tested rules (no-guessing, no-stalling, no-preference-asking, no-false-completion, no-skipping, no-dismissing, no-cosmetic, no-caveats, no-flagging). Use when user asks to "install guardrails", "set up agent guardrails", "add behavioral hooks", "agent-guardrails install", or wants to enforce assistant discipline.
Test installed agent guardrail hooks by sending trigger phrases through the stop hook script. Checks hook installation first, then runs two test phrases per rule. Use when user asks to "test guardrails", "verify hooks", "check guardrail patterns", "agent-guardrails test", or wants to confirm hooks are working.
Re-analyze Claude Code session logs against existing agent guardrail rules to measure effectiveness, catch false positives, identify missed anti-patterns, and refine regex patterns. Use when user asks to "update guardrails", "refine guardrail rules", "check guardrail effectiveness", "agent-guardrails update", "tune guardrails", or wants to improve existing behavioral rules based on real usage data.
Use when the user wants to write a "product spec" or "product specification", frame a "product bet", or define a falsifiable hypothesis before building. Also triggers on "replace the PRD", "retire the PRD", "the PRD is too long / too vague", "tighten this spec for an engineer or agent", "what's the bet", "what problem are we solving", "acceptance criteria", "success criteria", "kill / scale / graduate thresholds", "measurement plan", or when scoping a feature's problem, bet, success behaviors, and evaluation before any behavioral spec. Part of the spec-dd workflow; precedes /spec-dd:spec.