> For the complete documentation index, see [llms.txt](https://kb.packfiles.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.packfiles.io/using-warp/migration-hq/github-copilot-agent/migration-diagnosis.md).

# Migration Diagnosis

**When a migration fails, use the *****Diagnose Migration***** skill to classify the root cause and post a structured remediation plan as a comment on the issue so your team knows exactly what went wrong and what to do next.**

Migration failures can be opaque. A comment on a backlog issue might say "migration failed" and link to a runner log with hundreds of lines. The agent cuts through that noise by reading the evidence and surfacing only what matters.

## How to Use It

1. Open the backlog issue in Migration HQ for the repository whose migration has failed.
2. Assign the issue to the **Packfiles Warp** agent with the instructions: *"Diagnose the migration failure."*

The agent categorizes the failure and posts a diagnosis comment directly on the issue.

## What the Diagnosis Contains

The agent posts a comment on the issue with:

* **Root cause** — a single sentence stating what went wrong
* **Remediation steps** — a numbered list of specific actions to resolve the issue, including any Warp Vault changes, slash commands, or source system changes needed
* **Retry instruction** — the exact comment to post on the issue to retry the migration once remediation is complete

For most failure categories, the retry instruction is simply `/migrate`.

{% hint style="warning" %}
The `too-big` label (applied by Warp when a repository exceeds 10 GB) is always addressed in the diagnosis, even if another failure category is the primary cause. Size issues are a hard blocker that must be resolved regardless of what else is failing.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.packfiles.io/using-warp/migration-hq/github-copilot-agent/migration-diagnosis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.