45 skills · sorted by relevance
Create a separate Git working directory for feature development without switching your current branch. The skill checks branch names and ignore settings, prepares dependencies, and starts background checks, with options for separate dependency installation.
Create and manage Git worktrees, separate folders for working on different branches. Organize them under a shared project path, move uncommitted or stashed changes between them, copy environment files, and open them in an editor.
Manage Git worktrees, separate folders for working on different branches, with commands to create, list, and remove them. Move uncommitted changes between folders, copy environment files, and open a worktree in an editor.
Check background type checks, tests, and builds in a Git worktree, a separate working directory. Read verification logs to see results, failure counts, and errors, with suggested next actions while development continues.
Remove a specific Git worktree, a separate working directory for a branch, after checking uncommitted work and merge status. Clean up branches and stale references, protect important branches, and provide reminders for related database cleanup.
Clean up Git worktrees, separate working folders for branches, by identifying merged branches and reviewing unmerged ones. Preview deletions, preserve protected branches, and receive a report of removed folders and reclaimed disk space.
Use when legacy prompts or older framework flows reference `using-git-worktrees` and you need the modern runtime to resolve that capability cleanly.
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.
Prepare a separate workspace for feature development using platform tools or git worktree, which gives a branch its own working directory. It checks existing isolation, prepares dependencies, and runs tests before implementation begins.
Turn a feature idea into a design document through focused dialogue. The skill clarifies goals and constraints, compares two or three approaches, and reviews the design in sections before documenting architecture, data flow, errors, and testing.
Manage parallel feature development with Git worktrees, separate working folders for different branches. Assign distinct ports, copy environment files, optionally install dependencies, and check for uncommitted changes and merged branches before removing outdated worktrees.
Execute an implementation plan by assigning each independent task to a fresh helper agent in sequence. Review specification compliance and code quality after each task, track decisions in files, and finish with a review of the entire branch.
Prepare a separate Git working directory for feature development, then install project dependencies and run baseline tests. Check for existing isolation first, use native worktree tools when available, and otherwise fall back to Git.
Use Git worktrees to isolate parallel coding tasks. Use when setting up a task checkout, working in a shared repo, or managing existing worktrees.
The English summary is being prepared. Showing the original description.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
The English summary is being prepared. Showing the original description.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
The English summary is being prepared. Showing the original description.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans.
The English summary is being prepared. Showing the original description.
Use when working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, or comparing implementations across branches - provides git worktree commands and workflow patterns for parallel development with multiple working directories.
The English summary is being prepared. Showing the original description.
Use when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.
The English summary is being prepared. Showing the original description.
Manage parallel development with Git worktrees: creation with port allocation, environment sync, branch isolation, and cleanup. Use when working multiple branches at once, running parallel CI validations, or isolating agent workspaces.
The English summary is being prepared. Showing the original description.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
The English summary is being prepared. Showing the original description.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
The English summary is being prepared. Showing the original description.
Creates isolated git worktrees with smart directory selection and safety checks. Use when starting isolated feature work.
The English summary is being prepared. Showing the original description.
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.