Jev + Opus 5.5 做依赖迁移 agent 的 JSON 提示词
给出完整 JSON 工作流：Opus 5.5 按官方指南小步改代码，Jev 依据 diff、测试证据和预算在 inspect/migrate/verify/escalate 间选下一步。
HOW TO TURN JEV + OPUS 5.5 INTO A DEPENDENCY MIGRATION AGENT JSON prompt: { "goal": "Pilot one dependency or API upgrade with a reviewable record of behavior changes.", "inputs": { "repo": "<repository path>", "current": "<pinned version>", "target": "<selected version>", "guide": "<official upgrade guide>" }, "preserve": ["public contracts", "data formats", "expected behavior"], "workflow": [ "Read the guide and map affected call sites, config, data contracts, and runtime behavior.", "Pin the base commit. Run existing checks and record a baseline before editing.", "Have Opus 5.5 migrate one coherent surface at a time in an isolated branch.", "After each change, run build, type, and relevant regression checks. Compare results with the baseline." ], "jev": { "state": ["current diff", "test evidence", "compatibility gaps", "remaining budget"], "choices": ["inspect", "migrate", "verify", "escalate", "prepare_review"], "rule": "Choose the next bounded step from current evidence. Prepare for review only after passing checks are recorded." }, "return": ["version diff", "migration mapping with sources", "patch", "test commands and outputs", "unresolved gaps", "rollback steps"], "limits": [ "Confirm the documented Jev interface before using it. If unavailable, report and stop.", "Report missing evidence instead of guessing.", "Do not merge or deploy." ] } Opus 5.5 checks the official migration guide → updates affected code in small steps → Jev decides when to inspect, verify, or escalate based on recorded results If the checks pass, you get a patch with baseline comparisons, test logs, known gaps, and rollback instructions for review Save this before your next upgrade ↓
这条是引用着另一条写的：「让 agent 修 GitHub issue，Jev 选下一步动作」