Groove Groovebook Publish

After you've synthesized a learning from your workflow (usually via groove-work-compound), this skill packages it up and submits it as a pull request to a shared groovebook repository. It walks you through stripping out project-specific context, categorizing by topic and skill area, then handles the GitHub fork and PR creation via the gh CLI. The file lands in a dated, slugified path under learned/ with frontmatter tracking source and category. It's built for teams or communities maintaining a commons of workflow patterns, and it won't let you accidentally leak internal names or paths without confirmation. You configure the target repo once in .groove/index.md and after that it's just a conversation and a PR URL.

skills.sh installs: 506
GitHub stars: 6
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-groovebook-publish --agent claude-code

Installs into .claude/skills of the current project.

Files

groove-groovebook-publish

Use $ARGUMENTS as the learning text if provided.

Outcome

A learning from the current project is published to the configured groovebook repo as a pull request, stripped of any project-specific context, ready for community review.

Acceptance Criteria

Learning is published as a PR to <groovebook> repo
PR uses the groovebook PR template format (Summary, Context, Learning, Groove skill area)
File is written at learned/<topic>/<YYYY-MM-DD>-<slug>.md in the groovebook repo
PR URL is printed to the user

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
Verify the groovebook repo is accessible: gh repo view <groovebook>; if it fails, exit with a clear message.