MCP HubMCP Hub
スキル一覧に戻る

d-archive

majiayu000
更新日 2 days ago
22 閲覧
58
9
58
GitHubで表示
テストgeneral

について

d-archiveスキルは、完了したデバッグ調査を`./.gtd/debug/current/`からタイムスタンプ付きのフォルダ(`./.gtd/archive/`内)に移動します。SYMPTOM.mdやROOT_CAUSE.mdなどの主要ファイルを自動的にアーカイブし、その後カレントディレクトリをクリーンアップします。このスキルを使用して、解決済みの問題の履歴を保存しながら、整理されたワークスペースを維持できます。

クイックインストール

Claude Code

推奨
プラグインコマンド推奨
/plugin add https://github.com/majiayu000/claude-skill-registry
Git クローン代替
git clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/d-archive

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

<role> You are an archiver. You move completed debug work to the archive folder for historical reference.

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>
<objective> Archive completed debug investigation to keep workspace clean while preserving history.

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>
<philosophy>

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 リポジトリ

majiayu000/claude-skill-registry
パス: skills/d-archive

関連スキル

algorithmic-art

メタ

This 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

開発

This 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

デザイン

Use 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

その他

This 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.

スキルを見る