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.