task-cleaner

Archive completed task files and related artifacts into done/ by branch or feature name.

8|2|Updated Nov 1, 2023
One-click install
npx skills add https://github.com/Let-s-intern/lets-intern-client --skill task-cleaner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-cleaner
Source: https://github.com/Let-s-intern/lets-intern-client/tree/main/.claude/skills/task-cleaner
Command: npx skills add https://github.com/Let-s-intern/lets-intern-client --skill task-cleaner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

완료된 task 파일과 관련 자료(PRD, 스크린샷 등)를 브랜치명 또는 기능명 폴더로 정리하여 done/에 아카이브합니다. 사용자가 필요시 이 프로세스를 통해 체계적으로 보관하고 재활용합니다.

Core Features & Use Cases

  • 완료된 task 파일, PRD, 스크린샷 등을 브랜치명/기능명 폴더로 아카이브하여 관리합니다.
  • 폴더 이름 결정 로직은 사용자가 지정, 현재 Git 브랜치명, 또는 PRD/파일명에서 추출합니다.
  • 정리 완료 후 간단한 요약 보고서를 제공합니다.
  • Use Case: 프로젝트 관리와 문서 아카이빙이 필요한 팀에서 task 정리 작업을 빠르게 수행합니다.

Quick Start

현재 브랜치명에 해당하는 폴더나 사용자가 지정한 이름으로, 완료된 task 파일과 관련 자료를 done/ 폴더에 아카이브하도록 요청합니다.

Frequently Asked Questions about task-cleaner

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

FAQPage Schema
How do I archive completed task files and PRDs into a structured folder by branch name?

To archive completed task files, PRDs, and screenshots, you can organize them into a done/ directory using the current Git branch name or feature name as the folder identifier. This ensures completed task files are systematically stored and ready for reuse.

What is the best way to organize project screenshots and PRDs after finishing a feature?

Organizing project screenshots and PRDs after finishing a feature involves moving them into a dedicated done/ archive folder named after the branch or feature. This task management approach keeps completed artifacts separated from active work.

Can I use a custom folder name instead of the Git branch name for archiving task files?

Yes, you can specify a custom folder name for archiving task files instead of using the Git branch name. The folder naming logic can be user-defined, extracted from the current Git branch, or derived from the PRD or task file name.

How does task archiving by feature name work with existing task-management workflows?

Task archiving by feature name works by collecting completed PRDs, task files, and screenshots, then placing them into a done/ folder structured by branch or feature. It integrates into task-management workflows by providing a summary report after organization.

Do I need any external dependencies to archive task files and documentation into a done/ folder?

No external dependencies are required to archive task files and documentation into a done/ folder. The process relies on standard file organization driven by branch names or PRD file names, optionally leveraging scripts or references if present.

Why should I move completed PRDs and screenshots into a done/ archive instead of keeping them in the root?

Moving completed PRDs and screenshots into a done/ archive prevents workspace clutter and preserves task history by feature name. This organization method ensures completed artifacts remain accessible without interfering with active project files.