Qmigrate-legacy

Name: Qmigrate-legacy
Availability: InStock
Author: inho-team

Detect and relocate legacy QE artifacts into the current layout.

6|Updated Mar 14, 2026

Search Tags:#migration #cleanup #filesystem #legacy #migrate #qe-framework

Ready to run

npx skills add https://github.com/inho-team/qe-framework --skill qmigrate-legacy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Qmigrate-legacy
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qmigrate-legacy
Command: npx skills add https://github.com/inho-team/qe-framework --skill qmigrate-legacy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects artifacts from older QE structures and relocates them into the current layout.

Core Features & Use Cases

Auto-archive legacy QE artifacts into sessions/_legacy/ to keep projects tidy after upgrades.
Supports dry-run, single/multiple migrations, and safe, idempotent moves that avoid overwriting.
Provides a clear audit trail of what moved and where it went, for compliance and debugging.

Quick Start

Dry-run legacy migrations with /Qmigrate-legacy to review candidates, then apply to relocate artifacts into sessions/_legacy/.

Frequently Asked Questions about Qmigrate-legacy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate migration of legacy QE framework files into the current filesystem layout?▼

Legacy QE framework migration is automated by detecting older artifacts and relocating them into the current filesystem layout. The tool runs automatic migrations at SessionStart for eligible entries and can be invoked manually to audit or apply changes safely.

What is the best way to clean up outdated QE structures without losing files?▼

Cleaning up outdated QE structures is handled safely by archiving legacy artifacts into sessions/_legacy/. The process executes idempotent moves that avoid overwriting existing files, ensuring no data is lost during the cleanup operation.

Can I run a dry-run to preview legacy file migrations before applying changes?▼

Yes, you can run a dry-run to preview legacy file migrations before applying changes. Executing the migration command in dry-run mode reviews candidate artifacts and reports what will be moved without actually relocating any items.

When do I need to archive legacy QE artifacts into the sessions directory?▼

You need to archive legacy QE artifacts into the sessions directory after upgrading your project framework. This keeps projects tidy by relocating older structures, providing a clear audit trail of what moved and where it went for compliance and debugging.

Does the migration tool overwrite existing files when relocating legacy artifacts?▼

No, the migration tool does not overwrite existing files when relocating legacy artifacts. All migrations are executed safely and idempotently, ensuring that existing files remain untouched while reporting the moved items.

How does SessionStart auto-migration work for legacy QE structures?▼

SessionStart auto-migration works by automatically detecting and relocating auto-eligible legacy QE artifacts into the current layout. This background process keeps the filesystem tidy without manual intervention, moving items safely and idempotently.