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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
Design, review, or report a measured performance comparison. Use for benchmark methodology, speedup or regression claims, and performance-based choices; not generic performance discussion, ordinary dependency bumps, local renames, or prose edits.
The English summary is being prepared. Showing the original description.
Trace what an actual code change could break beyond its diff when interfaces, serialized data, database schemas, configuration, caches, lifecycle ordering, or cross-language consumers are involved. Use for explicit impact analysis; not local renames, prose edits, ordinary dependency bumps, or generic architecture discussion.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Plan or implement retirement of a system, API, feature, persisted configuration, or database shape. Use for compatibility cutovers, explicit deprecation review, or an explicit unreleased replacement decision, including determining whether consumers or data exist; not ordinary dependency bumps, local renames, prose edits, or generic architecture discussion.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.