/g The Contract Codex ← 返回动态 Catalog

Checkout Crash Regression Fix

Reproduce a checkout crash from a stack trace, identify the root cause, fix it, and add a regression test.

难度:intermediate 分类:investigation 来源:OpenHands tutorial library

完整 Prompt(可直接复制)

/goal
GOAL:
Complete Checkout Crash Regression Fix for an investigation task: Reproduce a checkout crash from a stack trace, identify the root cause, fix it, and add a regression test.

CONTEXT:
- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.
- Inspect logs, traces, reproduction notes, source paths, and the final report.
- Establish a baseline by running or locating evidence for: `crash reproduction test and checkout regression test`.

CONSTRAINTS:
- Keep the scope limited to this goal; do not expand into unrelated cleanup.
- Do not weaken tests, delete assertions, or mask errors to make verification pass.
- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.
- Separate observed evidence from hypotheses.
- Do not patch production code until the root cause is reproduced or strongly evidenced.

DONE WHEN:
- The implementation or documentation directly satisfies: Reproduce a checkout crash from a stack trace, identify the root cause, fix it, and add a regression test.
- The verification command or evidence path succeeds: `crash reproduction test and checkout regression test`.
- The final diff is scoped to the relevant files and has no unrelated formatting churn.

VERIFY:
- Run `crash reproduction test and checkout regression test` or the closest repo-local equivalent if the exact command is not available.
- Capture before/after evidence for the behavior, metric, report, or artifact involved.
- If verification cannot run locally, stop and report the missing dependency instead of guessing success.

OUTPUT:
- Summarize changed files, key decisions, verification output, and remaining risks.
- Include any follow-up that is required for production rollout or human review.

STOP RULES:
- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.
- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.
- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.

来源与证据

原始来源: OpenHands tutorial library

证据摘要: Fix the crash in the checkout process; source: OpenHands tutorial library; type: official-agent-task; verification: crash reproduction test and checkout regression test