qrspi-pr

사용 방법

설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.

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

시작 전 확인

설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.

원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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.