Feature Request: Proactive Claude Code migration guidance when workflow preservation context detected

Resolved 💬 3 comments Opened Jan 4, 2026 by bocast Closed Feb 18, 2026

Summary

When users are planning system migrations and discussing backup/restore workflows, Claude Code should proactively surface information about preserving Claude Code configuration, custom skills, and MCP settings - especially when a claude-code-guide agent is available.

Context

I was working with Claude Code (Opus 4.5) on a comprehensive migration plan for moving to a new workstation. The conversation included:

  • Reviewing backup scripts
  • Checking documentation for hardware/OS migration
  • Verifying configuration file preservation

Despite my prompt explicitly requesting a "thorough review" of migration documentation and scripts, Claude did not proactively consult its own documentation (via the claude-code-guide agent) to verify that Claude Code workflow would be preserved.

What Was Missed

  • Location of custom "/" skills (~/.claude/commands/)
  • Claude Code configuration files (~/.claude/settings.json, CLAUDE.md)
  • Docker MCP configuration interdependency (~/.docker/mcp/)
  • Post-migration steps specific to Claude Code

I had to explicitly ask "How will Claude Code know the skills we developed together?" before this information was surfaced.

Suggested Behavior

When a conversation includes keywords/context suggesting migration, backup, or workflow preservation, AND the user is actively using Claude Code, the model should:

  1. Proactively consult the claude-code-guide agent for migration-relevant information
  2. Surface critical Claude Code files that need migration consideration:
  • ~/.claude/ directory (especially commands/, settings.json, CLAUDE.md)
  • ~/.claude.json
  • ~/.docker/mcp/ (if Docker MCP is configured)
  1. Flag if custom commands/skills are detected but not mentioned in migration planning

Why This Matters

  • Custom skills represent significant user investment
  • MCP configuration is split across Claude Code and Docker Desktop (non-obvious)
  • Users may not realize their workflow customizations need explicit preservation
  • Claude Code is increasingly central to developer workflows

Environment

  • Claude Code version: 2.0.74
  • Model: claude-opus-4-5-20250101
  • Platform: Linux (Pop!_OS)

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗