task-cleaner

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

8|2|Updated Nov 1, 2023
Ready to run
npx skills add https://github.com/Let-s-intern/lets-intern-client --skill task-cleaner
πŸ’¬ Prompt for ChatGPT / Claude Chatβ–Ό
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.