409 skills · sorted by relevance
Split a large goal into clearly bounded tasks that can run in parallel. Coordinate existing agent and worktree tools, then combine and verify the results. The skill starts only when explicitly requested.
Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment", "set up branches", or when a freshly cloned repo has no sibling worktrees.
The English summary is being prepared. Showing the original description.
Creates isolated git worktrees in .claude/worktrees/ with intelligent branch naming, auto-incrementing, and commit type detection (feat/fix/refactor). Supports manual descriptions and auto-generation from uncommitted git changes. Use when user requests to create worktree, start isolated work, parallel development, run /worktree command, or mentions "worktree".
The English summary is being prepared. Showing the original description.
Explains the ~/.worktrees/<path-key>/<branch> worktree convention, the dotfiles-repo opt-in, and what a dotfiles worktree cannot validate. Use to understand or explain worktree layout and its constraints; use the git-worktree skill to actually create, switch to, or delete one.
The English summary is being prepared. Showing the original description.
Clean up git worktrees across your repos: list every worktree, classify it as merged, remote-only, local-only or dirty, recap what each holds, and remove only the merged clean ones after GO. Use for "clean up worktrees", "what is in my aos-wt folders", "land my worktrees", "prune worktrees".
The English summary is being prepared. Showing the original description.
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only for external windows or desktop UI that needs OS-level control, and Playwright or CDP for external pages.
The English summary is being prepared. Showing the original description.
Organize code changes into focused commits and manageable branches, prepare pull requests, and maintain release versions and changelogs. The skill also covers separate working directories for parallel work and checks before committing.
Compare changes across Git worktrees, branches, and pull requests through a facilitated discussion between agents. Produce one consolidation plan covering the target worktree, merge order, conflicts, and decisions that need human input.
Execute a written work plan by assigning implementation and verification to subagents. Track progress, isolate work in Git worktrees, record test evidence, and require independent verification before marking tasks complete, with optional pull request delivery.
Coordinate large migrations, refactors, and bulk renames by splitting them into independent tasks. After plan approval, 5–30 agents work in separate Git worktrees, isolated working directories, then review, test, and open a pull request for each task.
Establish the current repository state before starting or resuming Codewhale development. Check the active branch, uncommitted changes, related working directories, applicable instructions, and version consistency so editing begins with verified context.
Generate independent options for design, implementation, explanations, or debugging, then compare them using one shared rubric. Code candidates use separate working copies and undergo independent verification before a winner is presented for review.
Carry agreed implementation work through a separate Git worktree, an isolated working directory. After checks and review, it prepares one local commit, a clean branch, and a pull request draft for handoff without publishing them.
Hand an ongoing task to a fresh agent with a self-contained briefing. The skill gathers context, decisions, failed attempts, acceptance criteria, and constraints, then launches the receiving agent in the current workspace or a requested isolated workspace.
Delegate coding, analysis, refactoring, or reviews from Claude Code to Codex CLI. The skill explains unattended execution, permission settings, output capture, parallel tasks, and independent checks of changed files and test results.
Configure GSD through an interactive questionnaire. Choose a model profile and turn workflow features such as research, verification, and code review on or off, then merge the choices into the existing configuration.
Create and manage isolated GSD workspaces with repository copies and separate planning folders. Use one command to create an environment, review active workspace status, or remove a workspace and clean up its worktrees.
Fix git pre-commit hook failures in Flutter projects when using git worktrees. Use when: (1) Pre-commit hook with `flutter analyze` fails during `git commit` but passes when run manually, (2) Hook output shows "Resolving dependencies..." then immediately fails with no actual analysis errors, (3) Working in a git worktree (created via `git worktree add`). Root cause: git sets GIT_DIR to a worktree-style path during hook execution, which breaks `flutter pub get` (called internally by `flutter analyze`). Fix: unset GIT_DIR, GIT_INDEX_FILE, and GIT_WORK_TREE before flutter/dart commands in the hook.
The English summary is being prepared. Showing the original description.
Use for Codex-app worktrees. Triggers: worktree, rename worktree, detached HEAD, ~/.codex/worktrees, 워크트리, 워크트리 이름, 새 워크트리, 브랜치랑 워크트리.
The English summary is being prepared. Showing the original description.
Create, switch to, or delete a git worktree under ~/.worktrees/<path-key>/<branch>, then rebase the agent session onto that directory. Use when asked to make, enter, or remove a worktree for a branch, when work needs an isolated checkout, or when invoked as /git:worktree.
The English summary is being prepared. Showing the original description.
gtr のインストールと .gtrconfig を設定する。「worktree セットアップ」「gtr 設定」「gtrconfig 設定」「.gtrconfig 作成」「gtr インストール」「worktree 設定」などで起動。
The English summary is being prepared. Showing the original description.
Codex AppのWorktree用local environmentを作成・修復し、setup、Actions、並行実行時の状態分離を実Worktreeで検証する。
The English summary is being prepared. Showing the original description.
Coordinate coding projects through Claude DevFleet by splitting work into dependent tasks and dispatching Claude Code agents in separate Git working directories. Monitor progress, manage automatic task sequencing, and review structured reports of changes, tests, and errors.
Turn a vague request into a precise specification through five phases and file it as a GitHub issue. Optionally start a Claude Code agent in a separate working directory to begin implementation.