d-archive
About
The d-archive skill moves completed debug investigations from `./.gtd/debug/current/` to a timestamped folder in `./.gtd/archive/`. It automatically archives key files like SYMPTOM.md and ROOT_CAUSE.md, then cleans up the current directory. Use this skill to maintain a clean workspace while preserving a historical record of resolved issues.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/d-archiveCopy and paste this command in Claude Code to install this skill
Documentation
Core responsibilities:
- Check if current debug work is complete
- Create archive with timestamp
- Move all debug files to archive
- Clean up current debug folder </role>
Flow: Verify Complete → Create Archive → Move Files → Clean Up </objective>
<context> **Source:**./.gtd/debug/current/— Current debug work
Destination:
./.gtd/archive/debug-{timestamp}/— Archived debug work
Files to archive:
- SYMPTOM.md
- HYPOTHESES.md (if exists)
- ROOT_CAUSE.md (if exists)
- FIX_PLAN.md (if exists)
- FIX_SUMMARY.md (if exists) </context>
Archive When Done
Only archive when debug work is complete (bug is fixed) or abandoned.
Preserve History
Keep all files for future reference and learning.
Clean Current
After archiving, current/ folder should be empty for next debug session.
</philosophy> <process>1. Check Current Debug Work
Verify ./.gtd/debug/current/ exists and has files:
if [ ! -d "./.gtd/debug/current" ] || [ -z "$(ls -A ./.gtd/debug/current)" ]; then
echo "No debug work to archive"
exit 0
fi
2. Create Archive Directory
Generate timestamp-based archive name:
TIMESTAMP=$(date +%Y%m%d-%H%M%S)
ARCHIVE_DIR="./.gtd/archive/debug-${TIMESTAMP}"
mkdir -p "${ARCHIVE_DIR}"
3. Move Files
Move all files from current to archive:
mv ./.gtd/debug/current/* "${ARCHIVE_DIR}/"
4. Commit Archive
Commit the archive:
git add ./.gtd/archive/
git commit -m "chore: archive debug work to debug-${TIMESTAMP}"
5. Display Summary
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GTD ► DEBUG WORK ARCHIVED ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Archived to: ./.gtd/archive/debug-{timestamp}/
Files archived: {count}
Current debug folder is now empty and ready for next investigation.
─────────────────────────────────────────────────────
</process>
GitHub Repository
Related Skills
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
