Use native Worktrunk commands for explicit Git worktree operations when requested. Distinguish repository selection from worktree selection, and inspect command help before changing configuration or hooks.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
This is a small Codex adaptation of the upstream Worktrunk skill. Use wt --help and the relevant subcommand's --help for current syntax. The pinned release includes wt and git-wt.
wt -C PATH selects the repository or working directory for a command. A branch argument selects a worktree; do not treat it as a path or assume that -C selects that branch. Inspect wt list and the selected branch before switching, creating, or removing a worktree.
Worktrunk has user and project configuration. Inspect the relevant configuration and native help before changing either. Hooks may run commands and may require trust; request explicit approval before enabling or changing hooks. Do not use --yes to bypass that decision. Do not set up agent multiplexers or create LLM commits unless requested.
Follow the repository's own worktree and Git rules. If Improve owns a worktree, use its codex-improve lifecycle rather than independently changing that worktree.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.
日本語の概要は準備中です。原文の説明を表示しています。
Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.
日本語の概要は準備中です。原文の説明を表示しています。
Build and sharpen a project's domain model. Use only when actively changing glossary or ubiquitous-language terms, or recording a durable architectural decision; merely reading a glossary is not a trigger.
日本語の概要は準備中です。原文の説明を表示しています。
Explicit-only interview loop for stress-testing a plan, decision, or idea. Use only when the user asks to grill, interrogate, interview, or stress-test their thinking before action.
日本語の概要は準備中です。原文の説明を表示しています。