Prompt library

   },
   "migrate-a-pattern-across": {
     title: "Migrate a pattern across the codebase",
-    teaches: "Describe the old pattern and the new one. Asking Claude to identify every place first means the call sites are listed in the response, so you can check none were missed."
+    teaches: "Describe the old pattern and the new one. Asking Claude to identify every place first means the call sites are listed in the response, so you can check none were missed. For a migration across many files, run [/batch](/docs/en/commands). Claude splits the work into units for you to approve, then background subagents make the changes and open one pull request per unit."
   },
   "optimize-against-a-measurable": {
     title: "Optimize against a measurable target",

   "review-a-pull-request": {
     title: "Review a pull request",
     teaches: "Claude reviews with the whole codebase in context, not just the diff. It reads the changed code and what it calls, so it catches problems a diff-only review would miss.",
-    next: "Turn this on for every PR with Code Review"
+    next: "Run `/code-review <pr#>` in one command, or turn on Code Review for every PR"
   },
   "review-infrastructure-changes-before": {
     title: "Review infrastructure changes before applying",

 add rate limiting to the public API and make sure existing tests still pass
 ```
 
-**Give it a way to check its own work.** Ask for run, test, compare, or verify in the same prompt so Claude iterates instead of stopping after one attempt.
+**Give it a way to check its own work.** Ask for run, test, compare, or verify in the same prompt so Claude iterates instead of stopping after one attempt. To check the finished change against the running app, run [`/verify`](/docs/en/skills#run-and-verify-your-app).
 
 ```text wrap theme={null}
 write the migration, run it against the dev database, and confirm the schema matches