cleanup-progress

Summarize completed feature entries in PROGRESS.md files.

3|Updated Feb 12, 2026

Search Tags:#documentation #code completion #progress tracking #log management #feature summary

Ready to run

npx skills add https://github.com/giladresisi/ai-dev-env --skill cleanup-progress

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup-progress
Source: https://github.com/giladresisi/ai-dev-env/tree/main/skills/cleanup-progress
Command: npx skills add https://github.com/giladresisi/ai-dev-env --skill cleanup-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the issue of bloated and unmanageable PROGRESS.md files by consolidating verbose execution logs into concise, scannable completion summaries.

Core Features & Use Cases

Consolidate Progress: Replaces lengthy execution details with a brief summary of feature completion.
Preserve Key Info: Ensures essential details like status, validation, and notes are retained.
Archive Verbosity: Optionally archives detailed logs for future reference, keeping the main file clean.
Use Case: After a complex feature is fully implemented and validated, use this skill to update PROGRESS.md, making it easy for anyone to quickly understand what was done and how it was verified, without sifting through pages of logs.

Quick Start

Use the cleanup-progress skill to summarize the latest feature entry in PROGRESS.md.

Frequently Asked Questions about cleanup-progress

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

FAQPage Schema

How do I clean up a verbose PROGRESS.md file after feature completion?▼

To clean up a verbose PROGRESS.md file, replace lengthy execution notes with concise completion summaries. This extracts key information like feature name, validation methods, and test results, ensuring the main file remains scannable and uncluttered.

What is the best way to summarize feature completion notes in a progress tracking file?▼

Summarizing feature completion notes involves condensing detailed execution logs into brief entries that preserve essential validation methods and test results. This approach replaces verbosity with a scannable summary highlighting the feature status and verification details.

Can I archive detailed execution logs while keeping the main progress file clean?▼

Yes, you can archive detailed execution logs while keeping the main progress file clean. The process optionally moves verbose log details to an archive, ensuring only concise feature summaries remain in the primary document for easy reference.

Do I need any specific dependencies to consolidate progress tracking documentation?▼

No specific dependencies are required to consolidate progress tracking documentation. The process operates directly on the existing PROGRESS.md file format to extract feature names, completion status, and validation methods without external tools.

Why does my progress tracking file become unmanageable after complex feature implementation?▼

A progress tracking file becomes unmanageable because verbose execution logs accumulate during complex feature implementation. Replacing these detailed logs with concise completion summaries for finished features resolves the bloat and improves readability.