Groove Utilities Task Archive

This handles the cleanup work of archiving completed tasks from your Groove workflow into whatever backend you're using (beans, Linear, or GitHub). It reads your backend config from `.groove/index.md`, shows you what's about to be archived, and makes you confirm before doing anything. The smart bit is that it never runs automatically during daily standup routines, only when you explicitly ask for it, which prevents accidental bulk archiving. It adapts to each backend's quirks: beans archives everything in one go, Linear marks issues as archived, and GitHub closes them. You get a count of what was archived when it's done. Good for keeping your task list clean without the anxiety of automatic cleanup.

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

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-utilities-task-archive --agent claude-code

Installs into .claude/skills of the current project.

Files

groove-utilities-task-archive

Outcome

All completed and scrapped tasks are archived in the configured backend. The count of archived tasks is reported to the user.

Acceptance Criteria

All completed/scrapped tasks are moved to archived state in backend
User is shown the scope of what will be archived and confirms before running
Count of archived tasks is reported after completion

Constraints

Read tasks.backend from .groove/index.md to determine backend
If tasks.backend: none, no-op with friendly message
Always show user what will be archived and ask for confirmation before proceeding
Never run automatically during daily end — only when user explicitly requests
Backend mappings:
- beans: beans archive (archives all completed/scrapped — no single-task option)
- linear: mark filtered issues as archived via linear CLI or MCP
- github: close resolved issues via gh issue close
Report count of archived tasks after completion