원클릭으로
worktree
Details on the `worktree` package area of the **rusty-biscuit** repo
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Details on the `worktree` package area of the **rusty-biscuit** repo
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when working in the claudine/ package area or with the Claudine library/CLI — normalizing agentic-CLI lifecycle events and hooks, wrapping providers (Claude Code, Codex, Gemini, Goose, Kimi, OpenCode, Qwen, Kilo, Pi, Antigravity), composing Markdown prompts (compose/inline-compose/sequence), managing the MCP catalog, linking skills/commands/agents across providers, or researching agentic CLI platform behavior.
Expert knowledge for building and managing monorepos across JavaScript, TypeScript, Rust, Go, and JVM — workspace standards (npm, pnpm, Yarn, Cargo, Go workspaces, Gradle, Maven), task-orchestration tools (Nx, Turborepo, Bazel, Pants, Rush, Lerna, moon), and versioning (Changesets). Use when structuring a monorepo, choosing task-orchestration tooling, or setting up workspace versioning and release flows.
Use when deploying a Rust project to package managers (cargo, brew, apt, nixos, uv, npm), speeding up Rust builds with compilation caching (kache, RUSTC_WRAPPER, local/remote S3 caches, CI build cache), or interacting with Git from Rust (git2/libgit2 bindings, gitoxide/gix pure-Rust). Covers release distribution, build-time tooling, and programmatic Git access for Rust projects.
Expert knowledge for Rust systems programming — ownership, borrowing, type safety, error handling, async patterns, performance optimization, and 2024-edition improvements. Use when writing or reviewing idiomatic Rust, resolving borrow-checker or lifetime issues, structuring error handling, or optimizing performance.
Monorepo testing guide: L1/L2/L3 taxonomy, canonical just recipes, `require_level!` gating, nextest filtersets, and fuzzing. Load this before writing or reviewing tests in the rusty-biscuit workspace.
Expert guidance for the cross-platform `sniff` Rust library and CLI. Use when discovering host hardware, OS, network, programs, services, filesystems, Git repositories, worktrees, monorepo packages, remote providers, or when changing Sniff request tiers, observation reuse, work counters, CLI output, and macOS/Linux/Windows behavior.
| name | worktree |
| description | Details on the `worktree` package area of the **rusty-biscuit** repo |
Like many package areas in Rusty Biscuit, the worktree package area has two distinct packages:
worktree is the library where the business logic for how we handle git worktrees is regulatedworktree-cli (binary name of wt) is the CLI which leverages the worktree library for most of it's functionalityThe worktree-cli crate contains both a binary target (src/main.rs, binary wt) and a library target (src/lib.rs). Shared modules such as commands and perf are declared in both lib.rs and main.rs so they are available to integration tests (which use the library target) and to the binary.
worktree::worktree::list_worktrees uses worktree::cache to persist SHA-pair branch comparison results under the user cache directory. The cache key is (default_tip_sha, branch_tip_sha, CACHE_FORMAT_VERSION), so branch/default tip movement self-invalidates ahead/behind and clean-merge results. Dirty working-tree status is never cached and remains a live git status check.
list_worktrees is a thin wrapper over parse_worktree_state and fill_worktree_statuses. The CLI uses that seam to start graph/verbose data gathering from the parsed branch names while the expensive per-worktree status pass runs.