413 skills · sorted by relevance
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.
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.
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.
Resolve Git merge conflicts between two agents by comparing both changes and their stated goals. Combine compatible work, explain choices where designs differ, and verify the merged result with project builds or tests.
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.
Rebuild and install the Remotion Canvas Capture Chrome extension in a durable location, restore it after a working directory is deleted, and reload it in a compatible browser. It also prepares a webpage and still preview before manual recording.
Coordinate multiple agents in tmux, a terminal session manager, using shared tasks and persistent messages. Assign work, monitor progress and blockers, verify worker results, and shut down the team after tasks and state updates are complete.
Run the current working copy locally with a real language model and Postgres database. Choose web, Slack, or both to test a branch end to end, with separate Slack apps for concurrent instances.
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.
Review code changes in Plannotator’s browser interface and have the agent address returned comments. Choose the current working directory, another checkout, or a pull or merge request URL, with options to focus on a specific comparison base.
Carry out a validated development plan in an isolated Git worktree, a separate working directory. Coordinate parallel implementation, run quality checks, update documentation, and take the changes through pull request creation, merging, execution metrics, and cleanup.
Prepare an isolated local environment for manually testing DevSpace changes. Copy existing settings and state into the current checkout, build interface assets, start the development server, and refresh the test snapshot when needed.
Decide whether a task deserves its own git worktree and, if chosen, run it end to end: branch from the integration branch rather than the current tree, keep the main working copy untouched while the task runs, compare the result against the untouched baseline before declaring it done, and prepare it for a pull request instead of merging. Use when a request says to do the work in a new worktree or branch, when a change is large or risky enough that the main tree should stay usable, when several tasks need to run in parallel on one repository, when a result has to be diffed against current behavior, and when deciding where screenshots, builds, and other artifacts produced in a worktree should end up.
The English summary is being prepared. Showing the original description.
After /start-task: park the current clean, pushed feature branch in its own issue-numbered nested worktree (.worktrees/<issue#>) and return the primary checkout to current main, so the next parallel lane can start. Use when the user says to move the branch or task to a worktree or open a parallel lane.
The English summary is being prepared. Showing the original description.
After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/<issue#>), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.
The English summary is being prepared. Showing the original description.
Set up a new git worktree for parallel development. Creates the worktree, copies .env files, installs dependencies, and generates Prisma client. TRIGGER when user asks to set up a worktree, work on a branch in isolation, or needs a separate environment for a branch or PR.
The English summary is being prepared. Showing the original description.
Audit all git worktrees in the current project. Use when the user asks about worktree status, which branches are merged, which have uncommitted changes, or which worktrees can be safely cleaned up.
The English summary is being prepared. Showing the original description.
Structures git branches and worktrees: keeps unrelated changes on separate branches, isolates each in its own worktree created so the repository's setup runs, records dependencies with git-machete, and recombines them into a temporary mixdown branch for local testing. Use before creating any branch or worktree in a codebase that works on more than one branch, including branching off the default branch to start a change; when starting work in a fork, clone, or third-party checkout; when choosing what a new branch should be based on; when a branch is growing a second unrelated concern; when deciding whether to stack branches or keep them independent; when preparing a change for a pull request or patch submission; when handed an existing worktree or branch to implement and commit in a fork; or when a local build needs several in-progress branches combined. Not needed where the repository clearly commits everything to the trunk, or holds notes or personal data rather than code.
The English summary is being prepared. Showing the original description.
GitHub Issue を作成する。タスクは Issue 本文内でチェックボックスに分割。「Issue 作成」「Issue を作って」「タスクを Issue に」「Issue 追加」「チケット作成」「Issue を切る」「タスクを分割して Issue」などで起動。「ブランチも」「worktree も」と伝えれば作成後にブランチ/worktree も用意する。
The English summary is being prepared. Showing the original description.