bugfix
無料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.
日本語の概要は準備中です。原文の説明を表示しています。
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."
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Elixir debugging workflow and tools. Use when: debug, debugging, pry, inspect, trace, why is this failing, what's wrong, investigate, diagnose.
日本語の概要は準備中です。原文の説明を表示しています。
Implementer - fetches a GitHub issue, builds an implementation plan, then implements using TDD. Use when: implement, build this, code this, add this feature, TDD, test first, red green refactor, pick a task, next task, dev.
日本語の概要は準備中です。原文の説明を表示しています。
Extract learnings from the current session and update memory/config. Use when: learn from this, what did we learn, update memory, session retrospective, extract patterns, save learnings.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。