Loading...
Loading...
Found 250 Skills
Lease, list, return and destroy git worktrees with `treehouse`'s pre-warmed pool. Use when the project's worktree tool is `treehouse`, or when another skill says to make or remove a worktree with it.
current release-driven profileでWorktrunkをWSL/Linux workspace lifecycle Practiceとして使い、Rust/Cargo worktreeのbuild-output isolation・cache reuse・cleanupを含め、同等以上のguaranteeを持つalternativeへのrefinementも判断する時に使用する。
Implement the result of /to-spec and /to-tickets in code.
Create a new Git branch or code worktree for experiments, features, baselines, rebuttal fixes, or method revisions. Use when starting an isolated code direction, creating a branch, creating a project-aware code worktree under a project control root, or setting up a worktree with UV sync, IDE config copying, linked assets, and worktree memory.
Diagnostica, sem alterar nada, se este computador e este repositório estão prontos para trabalhar com SDD: repositório git, agente de código, identidade do git, worktrees órfãs, dependências, editor e dado exposto (senha, certificado A1 ou chave privada já salvos no git; .env fora do .gitignore; npm sem ignore-scripts; repositório público). Responde em uma linha quando está tudo certo e, quando não está, lista o que impede primeiro, cada item com o comando exato que resolve. Use quando o usuário pedir para checar o ambiente, antes de abrir a primeira frente de trabalho num projeto, ou quando algo estranho acontecer (commit que falha, comando não encontrado, worktree que sumiu).
Continue work from an earlier T3 Code thread by resolving its UUID, identifying the correct checkout or worktree, and producing a handoff for the normal agent.
Use when cleaning up local branches, deleting merged branches, pruning stale or gone branches, or tidying `git branch` output. Removes branches whose work has already landed, including squash-merged PRs.
Clean up a git repository: delete branches whose PRs merged (incl. squash-merges), remove their safely removable linked worktrees, list or delete local branches past a confirmed age threshold, prune stale remote-tracking refs and worktree metadata, and optionally prune local tags absent from the remote, run gc, or delete merged remote branches. Use when asked to clean up / prune / tidy git branches or worktrees, remove merged or stale branches, delete old branches, prune origin/* refs, or clear out a repo's branch/worktree list, including from a directory containing worktrees from one or more repositories. Reports first (dry run); never touches current/default/kept branches or main, dirty, locked, detached, unavailable, or submodule-containing worktrees. Ignored node_modules and dist output is disposable; other ignored files remain protected.
Isolate concurrent agent sessions in dedicated Git worktrees under .agents/worktree/ to prevent workspace collisions.
Clean dangling workspaces/worktrees, stale branches, excess build artifacts, caches, and other leftover clutter. Arguments: scan/plan (inventory only), workspaces, artifacts, caches, branches, deep, and all. Use when the user says "tidy up", reclaim disk, remove stale worktrees, clear build junk, or prune leftover agent/dev debris. Always inventory first; delete only with approval unless the user already ordered that exact cleanup.
Organize checkout/worktree topology, dependent branch/PR stacks, and unified delivery boundaries for change workstreams using Git/GitHub: identify normalized repositories and isolate regular implementations with an owning worktree by default, with worktree also permitted by default for explicit PR requests; determine commit, push, and PR actions in order of user-specified explicit endpoints, default Draft PR for normalized repositories, and local-only default for non-normalized repositories; publish safely from main/master; follow up on conflicts, CI status, and local commit/push for existing PRs. Applicable to worktree creation, migration, secure cleanup, "branch already checked out" scenarios, post-implementation Git delivery, splitting stacked/dependent PRs, using `gh stack` to create, view, sync, or land stacks, as well as PR merge conflicts, failed checks, fixing PRs to mergeable state, and uncommitted or unpushed fixes. It only owns Git topology and delivery, and does not take over domain implementation or project design; the exact syntax of `gh stack` is discovered from local `--help` output. Default delivery does not grant authorization to implicitly switch the main working tree branch, mark as Ready, merge, retarget, release, or force-push.
Revalidate and revise an existing implementation plan from feedback.