.claude/skills/d-archive/SKILL.md
Archive completed debug work to ./.gtd/archive/
npx skillsauth add Hoang604/get-thing-done d-archiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Core responsibilities:
Flow: Verify Complete → Create Archive → Move Files → Clean Up </objective>
<context> **Source:**./.gtd/debug/current/ — Current debug workDestination:
./.gtd/archive/debug-{timestamp}/ — Archived debug workFiles to archive:
Only archive when debug work is complete (bug is fixed) or abandoned.
Keep all files for future reference and learning.
After archiving, current/ folder should be empty for next debug session.
</philosophy> <process>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
Generate timestamp-based archive name:
TIMESTAMP=$(date +%Y%m%d-%H%M%S)
ARCHIVE_DIR="./.gtd/archive/debug-${TIMESTAMP}"
mkdir -p "${ARCHIVE_DIR}"
Move all files from current to archive:
mv ./.gtd/debug/current/* "${ARCHIVE_DIR}/"
Commit the archive:
git add ./.gtd/archive/
git commit -m "chore: archive debug work to debug-${TIMESTAMP}"
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GTD ► DEBUG WORK ARCHIVED ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Archived to: ./.gtd/archive/debug-{timestamp}/
Files archived: {count}
Current debug folder is now empty and ready for next investigation.
─────────────────────────────────────────────────────
<forced_stop> STOP. The workflow is complete. Do NOT automatically run the next command. Wait for the user. </forced_stop>
testing
manual trigger by user, do not auto invoke
tools
manual trigger by user, do not auto invoke
development
Trace execution paths and document how code actually behaves. Use when you need to understand how features work, walk through code flows, explain component behavior, trace where data comes from, understand relationships between components, or audit for orphaned events and dead code.
testing
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.