195 skills · sorted by relevance
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.
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.
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.
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.
Isolate parallel coding tasks with Git worktrees, separate working folders with their own branches. The skill guides environment setup, dependency installation, change review, merging, and cleanup so each task has a dedicated workspace.
Create, manage, and cleanup git worktrees with Claude Code agents across all projects. USE THIS SKILL when user says "create worktree", "spin up worktrees", "new worktree for X", "worktree status", "cleanup worktrees", "sync worktrees", or wants parallel development branches. Also use when creating PRs from a worktree branch (to update registry with PR number). Handles worktree creation, dependency installation, validation, agent launching in Ghostty, and global registry management.
The English summary is being prepared. Showing the original description.
Verify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my worktrees?", "where are my worktree learnings stored?", "turn off worktree memory sharing", "share learnings across my separate clones", or "point my worktrees at a custom store". For a team or cross-machine (git-tracked) sharing, use /memory-team instead.
The English summary is being prepared. Showing the original description.
Coordinate multiple AI agents with assigned owners, clear work boundaries, and a Kanban board that tracks progress. Organize separate branches or worktrees, collect test and handoff evidence, and define checks that must pass before combining their work.
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.
Set up Herdr Kit and its Mastra Code integration, manage repository synchronization, and create or remove managed worktrees, separate working copies for review or development. The workflow checks supported operations and verifies the resulting manager state.
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 across any repository with the `gwm` Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (`gwm exec`) or reclaim build artifacts (`gwm clean`), materialise a PR into a worktree (`gwm review`), drive a multi-repo workspace (`--workspace`), run the JSON daemon / statusline (`gwm daemon`, `gwm statusline`), list or pin AI-agent sessions per worktree (`gwm agents`, Claude Code / Codex / opencode / Mistral Vibe detection), seed config from a preset (`gwm init --preset`), diagnose with `gwm doctor`, drive tmux/zellij, or wire `gcd` via `gwm shell-init`. Also covers multi-forge (#419): GitHub via `gh` **or** GitLab via `glab`, the `forge` / `[forge_hosts]` keys, and `gwm trust add`. Triggers on `gwm`, `gwq`, `git worktree`, `.gwm.toml`, `forge`, `forge_hosts`, `glab`, `gwm trust add`, GitLab MR, `gwm create`, `gwm list`, `gwm exec`, `gwm clean`, `gwm review`, `gwm daemon`, `gwm statusline`, `gwm agents`, `gwm note`, `gwm bootstrap`, `gwm doctor`, `gwm switch`, `gwm tmux`, `gwm zellij`, `gwm link`, `gwm status`, `gwm shell-init`, `gcd`, `feat/#`, `fix/#`, GitHub issue/PR linking on a worktree.
The English summary is being prepared. Showing the original description.
Report which local git worktrees under tmp/ are safe to close, need a human look, or are explicitly protected. Use when the user says /fleet-audit, asks what worktrees can be cleaned up, or wants a status check across all Ralph-loop/spike worktrees before running closeout on any of them.
The English summary is being prepared. Showing the original description.
Meta-agent supervisor that manages a fleet of Claude Code agents running in tmux windows. Auto-discovers spare worktrees, spawns agents, monitors state, kicks idle agents, approves safe confirmations, and recycles worktrees when done. TRIGGER when user asks to supervise agents, run parallel tasks, manage worktrees, check agent status, or orchestrate parallel work.
The English summary is being prepared. Showing the original description.
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.
Create isolated git worktrees with smart directory selection and safety verification
The English summary is being prepared. Showing the original description.
Organize a task into parallel work streams with clear dependencies, separate places for changes, and explicit checks. Batch independent reads and tests, coordinate concurrent work, and report completed or blocked tasks with verification results.
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.
Manage Orca worktrees, separate working directories, along with terminals, repositories, and its embedded browser through the CLI. Use it to hand work to another agent, manage artifacts, run automations, and share skills within Orca.
Manage separate local development environments for multiple branches using the project's pnpm worktree CLI. Each environment has its own ports and dependencies, with options to share Supabase or isolate database changes for testing.
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.
Set up portless to give local development servers stable, named URLs instead of changing port numbers. It covers multiple apps, separate Git worktree URLs, HTTPS setup, and checks for proxy, domain resolution, and certificate problems.
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.
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.