skills.rest
gesmith0606
gesmith0606COMMUNITY
Explore all skills by this author →
GitHub

gsd-cleanup

Archives completed milestone phase directories from .planning/phases/ after a dry-run review and explicit confirmation.

Updated Aug 15, 2025
Search Tags:#automation#workflow#claude#cleanup#milestones#filesystem#archive
One-click install
npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-cleanup-gesmith0606
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/gesmith0606/nfl_data_engineering/tree/main/.claude/skills/gsd-cleanup
Command: npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-cleanup-gesmith0606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The gsd-cleanup skill consolidates and archives leftover phase directories from completed milestones to reduce clutter, preserve milestone snapshots, and maintain a tidy .planning directory structure.

Core Features & Use Cases

  • Identification: Detects phase directories associated with milestones that are marked as completed.
  • Safe Dry-Run: Presents a dry-run summary showing which directories would be moved before any changes are made.
  • Confirmed Archival: On user confirmation, moves selected phase directories into .planning/milestones/v{X.Y}-phases/ preserving history and organization.
  • Use Case: Run after a release or milestone closure when .planning/phases/ has accumulated historical phase folders that should be archived by milestone version.

Quick Start

Run the cleanup workflow to identify completed milestones, display a dry-run summary, and archive their phase directories into .planning/milestones/v{X.Y}-phases/ after confirmation.

Frequently Asked Questions about gsd-cleanup

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

FAQPage Schema
How do I archive completed milestone phase directories in my planning workflow?▼

To archive completed milestone phase directories, this Skill identifies completed milestones and moves their phase folders into .planning/milestones/v{X.Y}-phases/ after you review a dry-run summary and provide explicit confirmation.

What is the best way to clean up accumulated phase directories after a release?▼

Cleaning up accumulated phase directories after a release involves detecting completed milestones, displaying a dry-run summary of folders to be moved, and archiving them into versioned milestone subdirectories upon confirmation.

Can I preview which phase directories will be archived before making changes?▼

Yes, you can preview changes through a safe dry-run summary that shows exactly which phase directories will be moved before any filesystem modifications occur, ensuring no accidental archival.

When should I run milestone directory cleanup on my .planning folder?▼

You should run milestone directory cleanup when .planning/phases/ contains accumulated directories from past milestones that are marked as completed and need to be consolidated into versioned archive folders.

Does archiving phase directories preserve the original milestone history?▼

Archiving phase directories preserves milestone history by moving folders into .planning/milestones/v{X.Y}-phases/ rather than deleting them, maintaining a tidy structure while keeping snapshot data accessible.

Related Skills

Explore More Software Engineering Skills→
Poom5741Poom5741

gsd-cleanup

Archive completed milestone phase directories into versioned .planning/milestones folders.

Community
Intermediate
ev3rlitev3rlit

gsd-cleanup

Archive completed milestone phase directories into versioned .planning paths.

Community
Intermediate
yusaduymazyusaduymaz

gsd-cleanup

Archive completed phase directories into milestone-specific storage under .planning/milestones.

Community
Intermediate
electroheadfxelectroheadfx
4

gsd-cleanup

Archive completed milestone phase directories into versioned archive folders after dry-run confirmation.

Community
Intermediate