groove-groovebook-review

Outcome

Open learning PRs in the groovebook repo are listed; the user reviews one and submits a reaction (approve, comment, or request changes).

Acceptance Criteria

Open PRs are listed with title, author, and date

User selects a PR to review; diff and body are shown

User submits a reaction via

gh pr review

Steps

Read

groovebook:

from

.groove/index.md

; if absent, exit with:

groovebook is not configured. Add 'groovebook: /' to .groove/index.md to enable.

Check

gh auth status

; if not authenticated, exit with:

Not authenticated with GitHub. Run: gh auth login

List open PRs:

gh pr list --repo --state open --json number,title,author,createdAt

If none open: print "No open learning PRs in ." and exit

Display as a numbered list:

N. # — <title> (by , )

Ask: "Which PR would you like to review? (enter number or PR #)"

Show the PR:

gh pr view --repo

— show body

gh pr diff --repo

— show diff

Ask: "Your reaction? (approve / comment / request-changes)"

If

comment

ask for the comment text

If

request-changes

ask for the request text

If

approve

confirm intent Submit: gh pr review --repo -- --body "" For approve: gh pr review --repo --approve Confirm submission and print the PR URL. Optional follow-up: ask "Does this learning suggest a change to a groove skill? If so, consider opening a companion PR to the groove repo referencing this groovebook PR." Constraints Read-only until step 7 — do not modify any local files If gh pr diff output is very large (>200 lines), show only the first 50 lines and note it's truncated The approve reaction should always ask for confirmation before submitting — approvals are harder to undo than comments