What is groove-groovebook-review?

A workflow for reviewing open pull requests in a configured GitHub repository. A pull request is a proposed code change that others can inspect before it is merged.

It helps list open learning pull requests, inspect their descriptions and code changes, and approve them, comment, or request changes.

It gathers the proposal and code differences in one review flow, so the reviewer can make a recorded decision without manually finding each repository detail.

groove-groovebook-review — Skill for Claude Code by andreadellacorte

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add andreadellacorte/groove --skill groove-groovebook-review

Clone the repo

git clone --depth 1 https://github.com/andreadellacorte/groove

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-groovebook-review/github.svg)](https://agentmods.dev/skills/andreadellacorte/groove/groove-groovebook-review)

Your own site

<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-groovebook-review"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-groovebook-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-groovebook-review"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-groovebook-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 607 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 18 Mar 2026
Snyk warn 8 Mar 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.00607
Opus 5.5	$0.00012	$0.00243
Sonnet 5.5	$0.00006	$0.00121
Haiku 4.5	$0.00003	$0.00061

Measured 2mo ago against content hash fb448b33d97a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

groove-groovebook-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/groove-groovebook-review/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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: <owner>/<repo>' 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 <groovebook> --state open --json number,title,author,createdAt
```
- If none open: print "No open learning PRs in ." and exit
- Display as a numbered list: N. #<number> — <title> (by <author>, <date>)
Ask: "Which PR would you like to review? (enter number or PR #)"
Show the PR:
- gh pr view <number> --repo <groovebook> — show body
- gh pr diff <number> --repo <groovebook> — 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 <number> --repo <groovebook> --<approve|comment|request-changes> --body "<text>"

For approve: gh pr review <number> --repo <groovebook> --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

Read the full file on GitHub · 63 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 63 lines · 31 tokens per session scan A fb448b33d97a

Subscribe to this mod's changes

groove-groovebook-review is a skill published in the GitHub repository andreadellacorte/groove (6 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 607 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Git and workflow

groove-groovebook-review next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
groove-groovebook-reviewandreadellacorte/groove	Skill	6	3mo ago	MIT	A	31	Claude Code
prYeachan-Heo/oh-my-claudecode	Skill	41k	today	MIT	A	47	Claude Code
merge-batchdiegosouzapw/OmniRoute	Skill	83k	6d ago	MIT	A	46	Claude Code
otto-pr-review-loopomnigent-ai/omnigent	Skill	11k	today	Apache-2.0	A	17	Claude Code, Codex
engram-branch-prGentleman-Programming/engram	Skill	7.8k	today	MIT	A	37	Claude Code, Codex
github-contributordaymade/claude-code-skills	Skill	1.5k	today	MIT	A	105	Claude Code, Codex
revdiffumputun/revdiff	Skill	947	2d ago	MIT	A	250	Claude Code

groove-groovebook-review

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

groove-groovebook-review

Outcome

Acceptance Criteria

Steps

Constraints

What this file has done since we first saw it

groove-groovebook-review compared with skills from other repositories