| name | agent-migration-orchestration |
| description | Use when a coding agent needs to plan and run an end-to-end migration task using MigrateToWinUI without losing deterministic reports or source safety. |
Agent Migration Orchestration
Use this skill for end-to-end coding-agent migrations.
Standard Sequence
- Inspect the input shape: solution, project, directory, source framework, binary input, or mixed evidence.
- Build the toolchain.
- Analyze with explicit
--source when known.
- Write JSON plus Markdown plan/dashboard.
- Preview safe rewrites.
- Stage target projects with
compose.
- Validate staged outputs where available.
- Summarize manual blockers before any apply step.
Commands
python3 plugins/migrate-to-winui-agent/scripts/analyzer_codefix_workflow.py <input> --source auto --target both --mode preview --bundle
python3 plugins/migrate-to-winui-agent/scripts/analyzer_codefix_workflow.py <input> --source avalonia --target both --mode apply --rules AW2U0101 --rounds 2 --bundle
python3 plugins/migrate-to-winui-agent/scripts/migrate_workflow.py analyze <input> --source auto --target both
python3 plugins/migrate-to-winui-agent/scripts/migrate_workflow.py full <input> --source avalonia --target both --out out/migration
Guardrails
- Do not run destructive git commands.
- Do not rewrite original source unless the user explicitly asks for
apply.
- Keep generated outputs under
out/, artifacts/, or user-selected paths.
- If Avalonia and WPF evidence are mixed, pin
--source or report ambiguity.
