413건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Codex-app worktrees. Triggers: worktree, rename worktree, detached HEAD, ~/.codex/worktrees, 워크트리, 워크트리 이름, 새 워크트리, 브랜치랑 워크트리.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
gtr のインストールと .gtrconfig を設定する。「worktree セットアップ」「gtr 設定」「gtrconfig 設定」「.gtrconfig 作成」「gtr インストール」「worktree 設定」などで起動。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codex AppのWorktree用local environmentを作成・修復し、setup、Actions、並行実行時の状態分離を実Worktreeで検証する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
여러 Claude Code 에이전트에 개발 작업을 나누고 독립된 작업 환경에서 병렬로 실행합니다. 작업 의존성과 진행 상황, 변경 사항과 오류 보고서를 관리합니다.
두 에이전트가 각각 수정한 브랜치의 Git 충돌을 양쪽 변경 내용과 의도에 따라 중립적으로 해결합니다. 충돌별 판단 이유를 기록하고 빌드나 테스트로 통합 결과를 확인합니다.
모호한 요구를 다섯 단계로 정리해 구현에 사용할 명세와 GitHub 이슈를 만듭니다. 필요하면 독립 작업 디렉터리에서 Claude Code로 구현을 시작합니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GitHub Issue を作成する。タスクは Issue 本文内でチェックボックスに分割。「Issue 作成」「Issue を作って」「タスクを Issue に」「Issue 追加」「チケット作成」「Issue を切る」「タスクを分割して Issue」などで起動。「ブランチも」「worktree も」と伝えれば作成後にブランチ/worktree も用意する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage complex Git histories with guidance for reorganizing commits, copying selected changes between branches, and finding bug-introducing commits. It also covers working on multiple branches at once and recovering lost commits through Git's reference history.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.