Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

andreadellacorte/groove-groovebook-review

Name: groove-groovebook-review
Author: andreadellacorte

skills/groove-groovebook-review/SKILL.md

npx skillsauth add andreadellacorte/groove groove-groovebook-review

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

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 <groovebook>." 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

andreadellacorte/groove-groovebook-review

skills/groove-groovebook-review/SKILL.md

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

4 stars

testing

Updated Apr 24, 2026

$ install --global

skillsauth

npx skillsauth add andreadellacorte/groove groove-groovebook-review

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Apr 24, 2026, 8:33 PM0.4s1 file scanned

SKILL.md

name:: groove-groovebook-review
description:: Browse and review open learning PRs in the configured groovebook repo. Use to participate in the shared groove commons.
license:: MIT
allowed-tools:: Read Bash(gh:*) AskUserQuestion
author:: andreadellacorte

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 <groovebook>." 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

Related Skills

andreadellacorte/groove-utilities-stats

testing

VerifiedTrustedCommunity

Quantified compound-loop dashboard: lessons captured vs graduated, adherence streaks, and task velocity. Use to see whether the workflow is actually compounding.

5SKILL.mdUpdated Jun 5, 2026

andreadellacorte/groove-utilities-stats