gsd-cleanup

Archive completed milestone phase directories into versioned milestone archives.

Updated Feb 11, 2026

Search Tags:#workflow automation #github #project planning #archiving #repository maintenance #milestone management

Ready to run

npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-cleanup-artriv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-cleanup
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-cleanup-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents project planning clutter by archiving accumulated phase directories from milestones that are already completed.

Core Features & Use Cases

Milestone Phase Archiving: Moves old .planning/phases/ directories into the appropriate archive location under .planning/milestones/.
Dry-Run Summary Before Changes: Produces a preview of what will be archived so you can review impact before committing.
Safety via Confirmation: Archives only after you confirm the dry-run results.

Quick Start

Use the gsd-cleanup skill when .planning/phases/ has accumulated directories from past milestones.

Frequently Asked Questions about gsd-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I archive old milestone phase directories in GitHub project planning?▼

To archive old milestone phase directories, this skill moves accumulated folders from .planning/phases/ into versioned milestone archives under .planning/milestones/v{X.Y}-phases/. It only proceeds after you review a dry-run summary and provide explicit confirmation.

Can I preview repository maintenance changes before archiving completed milestones?▼

Yes, you can preview repository maintenance changes before archiving completed milestones using the built-in dry-run summary. This feature generates a detailed preview of what will be archived so you can review the impact on your project planning structure before committing.

What is the best way to reduce clutter from leftover phase folders in .planning/phases/?▼

The best way to reduce clutter from leftover phase folders is to run an automated archiving workflow that moves them into versioned milestone archives. This ensures completed milestone phases are reliably organized under .planning/milestones/ without manual file operations.

Does milestone management archiving work without additional dependencies?▼

Yes, milestone management archiving works without additional dependencies. The skill operates independently to move accumulated phase directories from .planning/phases/ into versioned archive locations, requiring only your explicit confirmation after reviewing the dry-run summary.

When should I not use automated archiving for project planning directories?▼

You should not use automated archiving for project planning directories when your milestone phases are still active or incomplete. The archiving process is designed exclusively for completed milestones to prevent clutter, and it waits for explicit confirmation after the dry-run to protect active data.

Why does my .planning/phases/ directory accumulate old milestone folders?▼

Your .planning/phases/ directory accumulates old milestone folders because completed project phases are left behind after milestones finish. Archiving these accumulated directories into versioned milestone archives under .planning/milestones/ reliably reduces this repository clutter.