菜单
Create a git commit following project conventions. Use when: commit, commit this, make a commit, commit changes, git commit, save changes, commit my work, stage and commit, detailed commit.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Bug hunter. Reproduces bugs with failing tests (RED), then fixes with TDD. Accepts a prompt, issue URL, or bug description. Use when: bugfix, fix bug, debug, broken, regression, failing, doesn't work, fix this.
Interactive pair review of a PR. Fetches the diff, scouts for context, then walks through each changed file one at a time. Collects review comments in a bag with conventional comment prefixes, previews them, and posts only after explicit approval. Trigger on: pair review, let's review together, walk me through the PR, review with me.
TDD pair programming with mode switching. Claude can be driver (writes code) or navigator (watches, questions, provokes). Supports GitHub issues, file watching, or arbitrary prompts. Scientific TDD, baby steps, one test at a time. Trigger on: pair, let's pair, tdd, you drive, I'll drive, dojo.
Orchestrator - spawns an autonomous orchestrator agent that decomposes a task into subtasks and drives multiple Claude agents to completion. Use when: overmind, orchestrate, multi-agent, delegate, spawn agents, break down task, run agents.
Deep code review - Elixir idioms, OTP patterns, tech debt, safety. Launches 3 parallel reviewers + plan-reviewer gate. Use when: review, review this, code review, check this code, review my changes, is this good, what do you think, techdebt, tech debt, code smells.
Elixir debugging workflow and tools. Use when: debug, debugging, pry, inspect, trace, why is this failing, what's wrong, investigate, diagnose.
| name | commit |
| description | Create a git commit following project conventions. Use when: commit, commit this, make a commit, commit changes, git commit, save changes, commit my work, stage and commit, detailed commit. |
Single-line commit message.
<type>: <short description>
/commit detailed or /commit -d)Multi-paragraph commit for significant changes. Review the conversation and staged diff, then write:
<type>: <short summary>
<paragraph explaining what changed and why>
<paragraph on technical approach, trade-offs, or notable decisions>
Use detailed mode for: milestone features, non-obvious fixes, architectural changes, anything where "why" matters more than "what".
Types: feat:, fix:, refactor:, test:, chore:, docs:
git add <files>, never git add .mix test
mix dialyzer
mix smoke
git diff --staged
git commit -m "feat: add mission genserver"
git commit -m "fix: handle port exit on crash"
git commit -m "refactor: extract ets state into module"
git commit -m "feat: add restart policies for missions
Missions can now be configured with --restart on-failure|always to
automatically restart on crash. Exponential backoff prevents tight
restart loops, starting at 1s and doubling up to the configured max.
Restart state (count, timestamps) persists in ETS across restarts
so the sliding window can enforce max-restarts limits. Logs accumulate
across restarts rather than resetting."