使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/lenbok/qrspi --skill qrspi-worktree開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Invoke with: thoughts/qrspi/<id>/
Worktree — Isolate the Implementation
Create a git worktree so implementation happens on an isolated branch without affecting your main working tree.
Input
The artifact directory path is provided by the user.
Process
- Determine identifiers from the artifact directory name:
- Branch name: derive from the directory name (e.g.,
ENG-1234-descriptionor2026-03-29-new-feature) - Repo name: detect from
basename $(git rev-parse --show-toplevel) - Worktree path:
~/wt/<repo-name>/<branch-name>
- Create the worktree:
git worktree add ~/wt/<repo-name>/<branch-name> -b <branch-name>- Confirm with the user before executing:
Ready to create worktree:
Worktree: ~/wt/<repo-name>/<branch-name>
Branch: <branch-name>
Plan: <path>/plan.md
To implement, invoke the `qrspi-implement` skill from the worktree.
Proceed?- Create the worktree after user confirms.
- Copy QRSPI artifacts to the worktree. Untracked files from the main tree do not appear in worktrees:
cp -r <artifact-directory> ~/wt/<repo-name>/<branch-name>/<artifact-directory>Output
- Git worktree created at
~/wt/<repo-name>/<branch-name> - QRSPI artifacts copied to the worktree
- Tell the user the worktree path and how to start implementation
Rules
- Always confirm before creating the worktree.
- Worktrees do not share untracked files with the main tree. Always copy the artifact directory after creating the worktree.
- Do not start implementation. That's a separate phase with a separate context window.
When to Go Back
If the plan doesn't exist yet at <path>/plan.md, tell the user to invoke the qrspi-plan skill first.
