{"version":"2.1.221","anchor":"migrate-now-ends-with-a-prompt-audit-and-a-todo-note-ships-i","canonical_anchor":"migrate-now-ends-with-a-prompt-audit-and-a-todo-note-ships-i","heading":"migrate now ends with a prompt audit, and a TODO note ships inside the prompt","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/migrate-now-ends-with-a-prompt-audit-and-a-todo-note-ships-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### `migrate` now ends with a prompt audit, and a TODO note ships inside the prompt\n\nThe migrate command now finishes by auditing your prompts and tool descriptions for stale wording.\n\n**What**\n\nAfter the per-target changes are applied, the `migrate` subcommand tells the model to audit in-scope prompt text, tool descriptions, and request code against `shared\/prompt-audit.md`.\n\n**Details**\n\n- A new Quick Task Reference row routes \"is this prompt outdated\" and \"remove the cruft\" questions to the same file.\n- An HTML comment left in the shipped prompt records that the skill's trigger description was deliberately not changed because it is eval-pinned, so the model sees this developer note as part of its context.\n\n**Evidence**\n\n`TODO(prompt-audit): remaining trigger question`\n\n- Area: Skills\n- Names: `\/claude-api migrate`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}