qrspi-pr

使い方

インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
必要なツール、認証情報、対応環境を原文で確認します。
入力と成果物を指定し、出力を資料と照合します。

npx skills add https://github.com/lenbok/qrspi --skill qrspi-pr

開始前の確認

導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。

リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Invoke with: thoughts/qrspi/<id>/

PR — Create the Pull Request

Create a pull request with a description grounded in the design document and the actual diff.

Input

Read <path>/design.md for context on what was built and why.

Process

Detect the base branch and gather PR information:

Detect base branch: git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@' (falls back to main)
git diff <base>...HEAD — the full diff
git log <base>...HEAD --oneline — commit history
Read <path>/design.md for the "why" behind the changes

Create the PR using gh pr create:

   gh pr create --title "<concise title under 70 chars>" --body "$(cat <<'EOF'
   ## Summary
   [2-3 bullets: what this PR does and why, drawn from design.md]

   ## Design Decisions
   [Key decisions from design.md that reviewers should understand]

   ## Changes
   [Brief description of what changed, organized by component if multi-component]

   ## How to Verify
   - [ ] [Automated verification command]
   - [ ] [Manual verification step]

   ## References
   - Design: `<path>/design.md`
   - Plan: `<path>/plan.md`
   EOF
   )"

Report the PR URL to the user.

Output

PR created on GitHub
URL reported to the user

Rules

Title under 70 chars. Use the body for details.
The summary should explain WHY, not just WHAT. The diff shows what changed; the PR description should explain the reasoning.
Reference the design and plan docs so reviewers can find the full context.
If the branch isn't pushed yet, push it first with git push -u origin <branch>.
If a PR already exists for this branch, update it with gh pr edit instead of creating a new one.