groove-groovebook-review

Included with Lifetime

$97 forever

Browse and review open learning PRs in the configured groovebook repo. Use to participate in the shared groove commons.

Code Review

What this skill does


# 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

1. Read `groovebook:` from `.groove/index.md`; if absent, exit with:
   `groovebook is not configured. Add 'groovebook: <owner>/<repo>' to .groove/index.md to enable.`

2. Check `gh auth status`; if not authenticated, exit with:
   `Not authenticated with GitHub. Run: gh auth login`

3. List open PRs:
   ```
   gh pr list --repo <groovebook> --state open --json number,title,author,createdAt
   ```
   - If none open: print "No open learning PRs in <groovebook>." and exit
   - Display as a numbered list: `N. #<number> — <title> (by <author>, <date>)`

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

5. Show the PR:
   - `gh pr view <number> --repo <groovebook>` — show body
   - `gh pr diff <number> --repo <groovebook>` — show diff

6. 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

7. Submit:
   ```
   gh pr review <number> --repo <groovebook> --<approve|comment|request-changes> --body "<text>"
   ```
   For approve: `gh pr review <number> --repo <groovebook> --approve`

8. Confirm submission and print the PR URL.

9. 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

Files: 1

Size: 2.3 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/andreadellacorte/groove/tree/main/skills/groove-groovebook-review

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts